| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2237 | Kartik K. Agaram | 2015-10-04 | 1 | -1/+1 |
| | | |||||
| * | 2226 - standardize warning format | Kartik K. Agaram | 2015-10-01 | 1 | -3/+3 |
| | | | | | | | | | Always show recipe name where error occurred. But don't show internal 'interactive' name for sandboxes, that's just confusing. What started out as warnings are now ossifying into errors that halt all execution. Is this how things went with C and Unix as well? | ||||
| * | 2218 - check types in instructions much earlier | Kartik K. Agaram | 2015-09-30 | 1 | -1/+1 |
| | | | | | | | | | | Front-loads it a bit more than I'd like, but the payoff is that other recipes will now be able to describe the type checks right next to their operation. I'm also introducing a new use of /raw with literals to indicate unsafe typecasts. | ||||
| * | 2217 | Kartik K. Agaram | 2015-09-29 | 1 | -0/+91 |