soumik15630m

8 ms·

1. 1.▲
   by soumik15630m 2mo ago

   thanks again! will consider these suggestions ... and also feel free to open issues and pr in the repo if you're interested
2. 2.▲
   by soumik15630m 2mo ago

   You were right on both of the issues you seemed unsure.. The issues you flagged are closed by version 1.1.1 - also mentioned in issue threads. On the codec suggestion ... it seems to go against my design motivation ...A file with "# --
3. 3.▲
   by soumik15630m 2mo ago

   not currently - currently lucen runs on marked for statement loop but yeah it's a cleaner one to add ...just not the surface i started with
4. 4.▲
   by soumik15630m 2mo ago

   Sure man thanks for the critique, genuinely.... To be precise..the core concurrency shapes, disjoint-chunk commit ordering and DAG-level wavefront scheduling, are model-checked (SequentialEquivalence; DependencySafety + Termination), contin
5. 5.▲
   by soumik15630m 2mo ago

   Sure those are good designs... But Lucen is not about "here's a nicer way to write loops," it's "you shouldn't have to touch the loop you already have."..... showing Lucen parallelize the ugly version is t
6. 6.▲
   by soumik15630m 2mo ago

   just wanted to make sure ... even if someone someday wishes to revert the decision of using lucen they will be okay with just removing the import hooks - and run everything as native -- and when they have time, they can clear the comments b
7. 7.▲
   Show HN: Lucen a Python compiler that parallelizes for-loops via comment pragmas(github.com)

   10 points by soumik15630m 3mo ago|17 comments