Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | survey.subx now working | Kartik Agaram | 2020-05-18 | 1 | -265/+51 |
| | |||||
* | emit-segments in survey.subx now working | Kartik Agaram | 2020-05-18 | 1 | -72/+104 |
| | |||||
* | second test also passing | Kartik Agaram | 2020-05-18 | 1 | -14/+79 |
| | |||||
* | compute-addresses now working? Maybe? | Kartik Agaram | 2020-05-18 | 1 | -92/+375 |
| | |||||
* | compute-offsets in survey.subx now working | Kartik Agaram | 2020-05-18 | 1 | -59/+100 |
| | |||||
* | - | Kartik Agaram | 2020-05-18 | 1 | -4/+13 |
| | |||||
* | - | Kartik Agaram | 2020-05-18 | 1 | -4/+4 |
| | |||||
* | - | Kartik Agaram | 2020-05-18 | 1 | -21/+23 |
| | |||||
* | - | Kartik Agaram | 2020-05-18 | 1 | -45/+0 |
| | |||||
* | - | Kartik Agaram | 2020-05-18 | 1 | -1/+1 |
| | |||||
* | - | Kartik Agaram | 2020-05-18 | 1 | -74/+0 |
| | |||||
* | yet another 'get' variant | Kartik Agaram | 2020-05-18 | 1 | -0/+318 |
| | |||||
* | assort.subx now working | Kartik Agaram | 2020-05-18 | 2 | -42/+197 |
| | |||||
* | dquotes.subx now working | Kartik Agaram | 2020-05-18 | 2 | -7/+22 |
| | |||||
* | tests.subx now working | Kartik Agaram | 2020-05-18 | 2 | -40/+57 |
| | |||||
* | apps that currently work | Kartik Agaram | 2020-05-18 | 1 | -68/+68 |
| | | | | | | | | | | | | | | | | | | | | Here are the obvious dependencies of different apps: allocate: mu slice-to-string: mu survey new-stream: mu assort dquotes tests get-or-insert-slice: mu survey assort get-or-insert: mu survey So we'll get these working in the following order: tests dquotes assort survey It doesn't look like sigils uses any functions with modified signatures, but it doesn't work at the moment. Let's get the core self-hosted passes working first before we look at syntax sugar. examples -> self-hosted passes -> syntax sugar -> mu | ||||
* | standard library tests all passing | Kartik Agaram | 2020-05-18 | 1 | -43/+64 |
| | |||||
* | table primitives working | Kartik Agaram | 2020-05-18 | 9 | -1237/+895 |
| | | | | $ ./translate_subx init.linux 0*.subx && ./a.elf test | ||||
* | start migrating handles to fat pointers | Kartik Agaram | 2020-05-18 | 4 | -36/+116 |
| | | | | | | | | | | | | | | | | | | | CI will fail from this commit onward. Currently working: $ bootstrap translate init.linux 0[4-7]*.subx 080zero-out.subx -o a.elf && ./a.elf test $ bootstrap run a.elf test $ chmod +x a.elf; ./a.elf test Plan: migrate functions that used to return handles to pass in a new arg of type (addr handle). That's a bit of a weird type. There should be few of these functions. (Open question: do we even want to expose this type in the Mu language?) Functions that just need to read from heap without modifying the handle will receive `(addr T)` or `(handle T)` types as arguments. As I sanitize each new file, I need to update signatures for any new functions and add them to a list. I also need to update calls to any functions on the list. | ||||
* | 6219 | Kartik Agaram | 2020-05-18 | 2 | -0/+3 |
| | |||||
* | 6218 - link to Mu's first fork | Kartik Agaram | 2020-05-10 | 1 | -0/+9 |
| | |||||
* | 6217 - make subx.vim work better out of the box | Kartik Agaram | 2020-05-10 | 1 | -26/+31 |
| | | | | | | Adding some more colors will improve the experience, but the choices depend on colorscheme, and first impressions should at least not seem to have degraded things. | ||||
* | 6216 | Kartik Agaram | 2020-05-05 | 2 | -12/+7 |
| | |||||
* | 6215 - show call stack in trace | Kartik Agaram | 2020-05-03 | 1 | -0/+4 |
| | |||||
* | 6214 | Kartik Agaram | 2020-04-27 | 1 | -1/+1 |
| | |||||
* | 6213 | Kartik Agaram | 2020-04-26 | 3 | -2/+34 |
| | | | | Some minor tweaks while preparing presentation to Mek's Junto group. | ||||
* | 6212 | Kartik Agaram | 2020-04-25 | 1 | -1/+1 |
| | |||||
* | 6211 | Kartik Agaram | 2020-04-25 | 1 | -6/+5 |
| | |||||
* | 6210 | Kartik Agaram | 2020-04-24 | 1 | -10824/+10986 |
| | |||||
* | 6209 | Kartik Agaram | 2020-04-24 | 1 | -1/+2 |
| | |||||
* | 6208 | Kartik Agaram | 2020-04-22 | 17 | -116/+123 |
| | |||||
* | 6207 - tweaks while creating a video | Kartik Agaram | 2020-04-19 | 3 | -5/+6 |
| | | | | https://futureofcoding.org/two-minute-week | ||||
* | 6206 | Kartik Agaram | 2020-04-17 | 6 | -115/+66 |
| | |||||
* | 6205 | Kartik Agaram | 2020-04-15 | 2 | -156/+31 |
| | | | | Rip out scaffolding for function overloading. | ||||
* | 6204 | Kartik Agaram | 2020-04-15 | 2 | -28/+0 |
| | |||||
* | 6203 | Kartik Agaram | 2020-04-12 | 2 | -115/+162 |
| | |||||
* | 6202 | Kartik Agaram | 2020-04-11 | 1 | -1/+0 |
| | |||||
* | 6201 | Kartik Agaram | 2020-04-09 | 2 | -6/+6 |
| | | | | Fix CI. Amazing how misleading the ofstream API is when coercing to bool. | ||||
* | 6200 - --dump is not needed for incremental traces | Kartik Agaram | 2020-04-09 | 4 | -11/+7 |
| | | | | | | | | This undoes commit 5764, which was ill-considered. We already had incremental prints at that point to 'last_run'. As long as we don't run out of RAM on large traces, there doesn't seem any need to print to stderr. Now '--dump' is only needed when juggling multiple traces. | ||||
* | 6199 | Kartik Agaram | 2020-04-08 | 1 | -1/+1 |
| | |||||
* | 6198 | Kartik Agaram | 2020-04-08 | 2 | -14/+10 |
| | |||||
* | 6197 | Kartik Agaram | 2020-04-08 | 2 | -18/+18 |
| | |||||
* | 6196 | Kartik Agaram | 2020-04-06 | 2 | -2/+2 |
| | |||||
* | 6195 | Kartik Agaram | 2020-04-06 | 2 | -1/+1 |
| | | | | This bug was never caught because we've never tested with more than 2 segments. | ||||
* | 6194 | Kartik Agaram | 2020-04-06 | 2 | -3/+6 |
| | |||||
* | 6193 | Kartik Agaram | 2020-04-06 | 2 | -3/+6 |
| | |||||
* | 6192 | Kartik Agaram | 2020-04-06 | 2 | -3/+6 |
| | |||||
* | 6191 | Kartik Agaram | 2020-04-06 | 2 | -5/+6 |
| | |||||
* | 6190 | Kartik Agaram | 2020-04-06 | 1 | -31/+33 |
| | |||||
* | 6189 | Kartik Agaram | 2020-04-06 | 2 | -15/+14 |
| |