<feed xmlns='http://www.w3.org/2005/Atom'>
<title>fwd/scripts, branch mvcheck</title>
<subtitle>A programming language that cannot return</subtitle>
<id>https://metanimi.dy.fi/cgit/fwd/atom?h=mvcheck</id>
<link rel='self' href='https://metanimi.dy.fi/cgit/fwd/atom?h=mvcheck'/>
<link rel='alternate' type='text/html' href='https://metanimi.dy.fi/cgit/fwd/'/>
<updated>2025-01-03T23:25:31Z</updated>
<entry>
<title>initial move checking</title>
<updated>2025-01-03T23:25:31Z</updated>
<author>
<name>Kimplul</name>
<email>kimi.h.kuparinen@gmail.com</email>
</author>
<published>2025-01-03T23:25:31Z</published>
<link rel='alternate' type='text/html' href='https://metanimi.dy.fi/cgit/fwd/commit/?id=aec19e55ca32f68536a550f100d3f058b8a93c02'/>
<id>urn:sha1:aec19e55ca32f68536a550f100d3f058b8a93c02</id>
<content type='text'>
+ 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?
</content>
</entry>
<entry>
<title>initial commit</title>
<updated>2024-12-03T20:04:38Z</updated>
<author>
<name>Kimplul</name>
<email>kimi.h.kuparinen@gmail.com</email>
</author>
<published>2024-12-03T20:04:38Z</published>
<link rel='alternate' type='text/html' href='https://metanimi.dy.fi/cgit/fwd/commit/?id=2253da61e9b3dd5408bed182ea08e5270156c17e'/>
<id>urn:sha1:2253da61e9b3dd5408bed182ea08e5270156c17e</id>
<content type='text'>
+ Lots of code copied from ek, so didn't have to start from scratch, but
  might mean there are some quirks here and there that made sense in ek
  but not necessarily here.
</content>
</entry>
</feed>
