aboutsummaryrefslogtreecommitdiff
path: root/examples/vec.fwd
AgeCommit message (Collapse)Author
4 daysadd initial reference invalidationKimplul
+ Makes vec example actually memory safe, which is cool + Specify owner > sub relationships with ">" in closure parameter lists, uses the same group idea as closure calls + Relies on users implementing functions in a consistent manner, since you can kind of do whatever with pointers. Presumably there would be a stdlib of vec/map/set etc. which applications could then use and by proxy be memory safe. Although some more checks wouldn't hurt, I suppose? + Not sure I like having reference invalidation be 'just a move', seems to work alright but the semantics of it are a bit muddy.
2026-02-26fix vec exampleKimplul
+ Compiler works fine, example was borked :) + Although, not a very good example I must admit, it bashes a hole into my nice memory analysis plan :(
2026-02-26add comment about hole in my assumptionsKimplul
2026-02-26example/vec fixesKimplul
+ Doesn't quite work yet, but compiles fine. Some issues were in the example itself, heh
2026-01-06improve move checker to detect pointer leaksgncKimplul
+ Currently requires a lot of unnecessary `forget` statements, but at least some can likely be eliminated by doing some basic origin analysis, kind of like with groups
2026-01-06allow omitting ';' in trivial callsKimplul
2026-01-06work towards a simple integer vector implementationKimplul
+ Hopefully shows that useful programs can be implemented with the rules present + Still missing at least external functions with non-void returns
2026-01-06implement enough type analysis for vector exampleKimplul
+ Big commit, scary + Some details still a bit up in the air, mainly about move checking structure member access ('register' types are freely copied I guess, same as in rust? How about user types?)