Brian Beckman

I've gotten to a certain point and I'm stuck. I wonder if you can see a way out. For monadic chaining, an alternative (in this case, to the nil-propagating arrow)...

no hurry here -- i'm recovering from h1n1 flu, which became pneumonia and has completely knocked me out for two solid weeks -- somehow i managed to crawl up from...

Have begun some experiments with the continuation monad -- definitely arrowable through m-chain :) Next challenge is arrowing delimited continuations as with https://github.com/swannodette/delimc. More from me as time permits. Thanks...

Looks like we DO have `field` and `default_factory` ! GREAT!

my test show that you do, e.g. `0x_BAD_BEEF` is fine in both LPython and in CPython. It's double underscore and trailing underscore that CPython forbids as syntax error, and LPython...

Seems like a `good first issue` for someone to learn the error-reporting system.

I fixed it in my branch and added .idea to .gitignore ``` (lp) ┌─(~/Documents/GitHub/lpython)─────────────────────────────────────────────────────────(brian@MacBook-Pro:s001)─┐ └─(09:22:54 on vector-backend ✖ ✹)──> git commit -am "remove .idea and add .idea to .gitignore" ──(Mon,Feb12)─┘...

I also see a read_file on line 197 of lpython.cpp. I'm still learning what's going on.

Looks like, during parsing, read_file is called at least twice, once to parse and once to `[gs]et_module_path`, and maybe more than once for that purpose. Some of the following breaks...

marking `enhancement` and `good first issue`. It likely means some architectural "re-plumbing" of the front-end. Some file metadata or even the whole file itself will have to be cached somewhere.