about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* assort.subx now workingKartik Agaram2020-05-182-42/+197
|
* dquotes.subx now workingKartik Agaram2020-05-182-7/+22
|
* tests.subx now workingKartik Agaram2020-05-182-40/+57
|
* apps that currently workKartik Agaram2020-05-181-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 passingKartik Agaram2020-05-181-43/+64
|
* table primitives workingKartik Agaram2020-05-189-1237/+895
| | | | $ ./translate_subx init.linux 0*.subx && ./a.elf test
* start migrating handles to fat pointersKartik Agaram2020-05-184-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.
* 6219Kartik Agaram2020-05-182-0/+3
|
* 6218 - link to Mu's first forkKartik Agaram2020-05-101-0/+9
|
* 6217 - make subx.vim work better out of the boxKartik Agaram2020-05-101-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.
* 6216Kartik Agaram2020-05-052-12/+7
|
* 6215 - show call stack in traceKartik Agaram2020-05-031-0/+4
|
* 6214Kartik Agaram2020-04-271-1/+1
|
* 6213Kartik Agaram2020-04-263-2/+34
| | | | Some minor tweaks while preparing presentation to Mek's Junto group.
* 6212Kartik Agaram2020-04-251-1/+1
|
* 6211Kartik Agaram2020-04-251-6/+5
|
* 6210Kartik Agaram2020-04-241-10824/+10986
|
* 6209Kartik Agaram2020-04-241-1/+2
|
* 6208Kartik Agaram2020-04-2217-116/+123
|
* 6207 - tweaks while creating a videoKartik Agaram2020-04-193-5/+6
| | | | https://futureofcoding.org/two-minute-week
* 6206Kartik Agaram2020-04-176-115/+66
|
* 6205Kartik Agaram2020-04-152-156/+31
| | | | Rip out scaffolding for function overloading.
* 6204Kartik Agaram2020-04-152-28/+0
|
* 6203Kartik Agaram2020-04-122-115/+162
|
* 6202Kartik Agaram2020-04-111-1/+0
|
* 6201Kartik Agaram2020-04-092-6/+6
| | | | Fix CI. Amazing how misleading the ofstream API is when coercing to bool.
* 6200 - --dump is not needed for incremental tracesKartik Agaram2020-04-094-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.
* 6199Kartik Agaram2020-04-081-1/+1
|
* 6198Kartik Agaram2020-04-082-14/+10
|
* 6197Kartik Agaram2020-04-082-18/+18
|
* 6196Kartik Agaram2020-04-062-2/+2
|
* 6195Kartik Agaram2020-04-062-1/+1
| | | | This bug was never caught because we've never tested with more than 2 segments.
* 6194Kartik Agaram2020-04-062-3/+6
|
* 6193Kartik Agaram2020-04-062-3/+6
|
* 6192Kartik Agaram2020-04-062-3/+6
|
* 6191Kartik Agaram2020-04-062-5/+6
|
* 6190Kartik Agaram2020-04-061-31/+33
|
* 6189Kartik Agaram2020-04-062-15/+14
|
* 6188Kartik Agaram2020-04-061-7/+18
|
* 6187Kartik Agaram2020-04-062-1/+3
|
* 6186Kartik Agaram2020-04-062-6/+2
|
* 6185Kartik Agaram2020-04-061-8/+8
|
* 6184Kartik Agaram2020-04-052-1/+0
| | | | Why the heck are we bumping this pointer? Seems like a bug.
* 6183Kartik Agaram2020-04-031-1/+1
| | | | Bugfix in CI setup.
* 6182 - start of support for safe handlesKartik Agaram2020-04-0342-221/+221
| | | | | | | | | | | | | | So far it's unclear how to do this in a series of small commits. Still nibbling around the edges. In this commit we standardize some terminology: The length of an array or stream is denominated in the high-level elements. The _size_ is denominated in bytes. The thing we encode into the type is always the size, not the length. There's still an open question of what to do about the Mu `length` operator. I'd like to modify it to provide the length. Currently it provides the size. If I can't fix that I'll rename it.
* 6181Kartik Agaram2020-04-0318-51/+54
|
* 6180Kartik Agaram2020-04-032-73/+11
| | | | | It's going to be hard work retrofitting 8-byte handles in place of 4-byte addrs. Here we just clean up some unused args.
* 6179Kartik Agaram2020-04-031-2/+2
|
* 6178Kartik Agaram2020-03-318-8/+40
|
* 6177Kartik Agaram2020-03-291-4/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-16 20:24:48 +0000