| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2025-03-18 | add move queues | Kimplul | |
| + Returning blocks don't want to show moves for subsequent statements, but do want to show them for possible closure callers above. | |||
| 2025-03-17 | fix some total moves | Kimplul | |
| 2025-03-17 | detect leaks | Kimplul | |
| 2025-01-09 | initial ptr stuff | Kimplul | |
| 2025-01-09 | initial reference checking | Kimplul | |
| 2025-01-06 | implement move checking furthermvcheck | Kimplul | |
| + Enough that examples still compile, but missing references etc. | |||
| 2025-01-04 | initial move checking | Kimplul | |
| + Missing implementations for most things, but it already highlights an oversight in my initial plan, namely that currently, a function might call multiple of its closures, meaning that a closure wouldn't be allowed to move a value. I'm debating whether to check that only one closure from a parameter list is called at a time or if I should do what Hylo does and add in some kind of 'subscript' that's like a function but has slightly different rules? | |||
 |
index : fwd | |
| A programming language that cannot return | kimi.h.kuparinen+fwd@gmail.com |
| aboutsummaryrefslogtreecommitdiff |