about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* 354 - stepping back, test-driving 'addr' helper againKartik K. Agaram2014-11-282-1/+29
|
* 353 - found lots of holes in array supportKartik K. Agaram2014-11-271-34/+34
| | | | | I've uncovered a few while enhancing 'interpolate', but I'll wait to fix them all before I commit the enhancements.
* 352 - 'interpolate' as a poor man's printfKartik K. Agaram2014-11-272-2/+174
|
* 351 - break/loop from nested blocksKartik K. Agaram2014-11-272-10/+58
|
* 350Kartik K. Agaram2014-11-271-9/+9
|
* 349 - jump to labelKartik K. Agaram2014-11-272-3/+49
|
* 348Kartik K. Agaram2014-11-272-7/+7
|
* 347 - allow 'arg' channel to be rewoundKartik K. Agaram2014-11-272-9/+26
|
* 346Kartik K. Agaram2014-11-271-7/+7
|
* 345Kartik K. Agaram2014-11-272-59/+2
|
* 344 - about to give up on rewrite rulesKartik K. Agaram2014-11-273-8/+30
| | | | | | | | | | | | | | | | | I wanted to come up with some way to rewrite 'def-clause foo' to 'after foo/more-clauses', something like: rewrite def-clause [ (fn-name string-address) <- arg (label-name string-address) <- strcat (fn-name string-address deref) ("/more-clauses" literal) (body expr) <- arg reply `(after ,label-name ,body) ] But the quasiquote is still a nested expression that doesn't fit our model well. Still an open question how to do template interpolation in mu.
* 343 - experiment: rewrite rulesKartik K. Agaram2014-11-272-2/+38
| | | | We'll worry later about implementing them in mu.
* 342 - strcatKartik K. Agaram2014-11-272-2/+79
|
* 341 - standardize traces againKartik K. Agaram2014-11-273-1/+51
|
* 340Kartik K. Agaram2014-11-262-2/+3
|
* 339 - string literals for convenienceKartik K. Agaram2014-11-262-7/+37
| | | | | | I'm cheating a little when it comes to strings, making use of Racket primitives. But in principle it seems like a local transform to implement even in machine code.
* 338 - starting to work on string primitivesKartik K. Agaram2014-11-262-1/+13
|
* 337 - rename 'continue' instructions to 'loop'Kartik K. Agaram2014-11-262-28/+28
|
* 336Kartik K. Agaram2014-11-261-1/+0
|
* 335 - tangle at labels scoped to functionsKartik K. Agaram2014-11-262-5/+37
|
* 334Kartik K. Agaram2014-11-261-0/+4
|
* 333Kartik K. Agaram2014-11-261-1/+2
|
* 332 - example function with multiple clausesKartik K. Agaram2014-11-262-0/+32
| | | | | | | | | | | I'm still figuring out the idioms, and it doesn't seem like there's an easy way to avoid redundant allocations and arg reading. At least for generic functions we want to optimize for each call-site, we can create subsidiary labels to jump to. Also, this is the first genuine use for random access to a function's arguments.
* 331Kartik K. Agaram2014-11-261-3/+1
|
* 330Kartik K. Agaram2014-11-261-12/+52
|
* 329Kartik K. Agaram2014-11-261-1/+1
|
* 328Kartik K. Agaram2014-11-261-35/+34
|
* Merge pull request #1 from KyleAMathews/patch-1Kartik Agaram2014-11-251-14/+28
|\ | | | | Convert readme to markdown for github.
| * Rename file so markdown will compileKyle Mathews2014-11-251-14/+28
|/
* 326Kartik K. Agaram2014-11-251-2/+2
|
* 325 - example program using channelsKartik K. Agaram2014-11-253-0/+79
|
* 324 - more elaboration in ReadmeKartik K. Agaram2014-11-251-22/+143
| | | | | I have different prose in Readme and at the top of the tests. Let's see how hard they are to manage over time.
* 323 - function clausesKartik K. Agaram2014-11-242-2/+33
| | | | | | | | | | | You can now call 'def' on a function name multiple times. Each time the instructions you provide are *prepended* to any existing instructions. One important use for this is when you define a new type and need to support it in all your generic methods. Now you can keep all those extensions in one place, near the definition of the type. To redefine a function, use 'def!'.
* 322Kartik K. Agaram2014-11-241-12/+12
|
* 321 - before/after can now come anywhereKartik K. Agaram2014-11-243-31/+35
| | | | | | This pollutes our traces with all 'system software'. Too much trouble to keep it out; just lump it for now. Who knows, might even be useful. Most of the time convert* labels are easy to grep out when debugging.
* 320Kartik K. Agaram2014-11-241-1/+1
|
* 319 - ack, forgot to handle blocks when tanglingKartik K. Agaram2014-11-243-13/+87
| | | | | | | | | | | | Will the 'lightweight tools' really be all that useable if we encourage people to layer them one atop another and track precisely what inputs each can accept? Something to keep an eye on. In the meanwhile, we have a new (but very unrealistic) example demonstrating the tangling directives. There's still a big constraint on ordering: before/after clauses have to come before functions that need them.
* 318Kartik K. Agaram2014-11-241-0/+7
|
* 317Kartik K. Agaram2014-11-241-79/+83
|
* 316Kartik K. Agaram2014-11-241-7/+7
|
* 315 - handle before/after uniformly like defKartik K. Agaram2014-11-242-63/+89
|
* 314 - better syntax for functionsKartik K. Agaram2014-11-247-412/+550
|
* 313 - tangling primitivesKartik K. Agaram2014-11-242-2/+218
|
* 312Kartik K. Agaram2014-11-242-7/+20
|
* 311Kartik K. Agaram2014-11-242-6/+6
|
* 310Kartik K. Agaram2014-11-242-10/+10
|
* 309 - publish to githubKartik K. Agaram2014-11-232-120/+419
| | | | Also mirror mu.arc.t.html to the gh-pages branch.
* 308 - temporarily inline charterm dependencyKartik K. Agaram2014-11-2311-0/+4154
|
* 307Kartik K. Agaram2014-11-231-1/+4
|
* 306 - 'sleep' now watches for changes to a locationKartik K. Agaram2014-11-232-97/+22
| | | | | | | | | | | | This simplifies things a lot and eliminates the race condition. I think it's practical too, as long as you save a single location and don't permit sleeping on compound structures. I'm resigned to needing a lock in the native setting. Should I be concerned that I fixed a failing test by getting rid of hit? If I had alternatives, how would I save the old sleep implementation?
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-07 16:40:42 +0000