Brad Chamberlain

Thanks for your comment @pclausen. As you hopefully saw in the OP, Chapel can be used on Windows 10 systems via Windows Subsystem for Linux (WSL) / Linux bash shell....

> How about using cpp std::thread instead of posix and forget about supporting different OS threads at all? Hi @MarcTCruz : That's an interesting idea, where we could even consider...

Thanks for the feedback @Aeva. I'm giving a talk at Microsoft tomorrow, and one of the things I'll be curious to explore is whether there's any appetite there for helping...

@psath : Thanks for pointing out this discrepency. I believe that this may be a case where the implementation is correct (or at least, "as intended") and the documentation is...

@psath: Thanks for the feedback. I hadn't looked at the docs prior to my previous comment. Is the part you're referring to, the following (emphasis mine): > .. code-block:: chapel...

That totally makes sense. Thinking a bit more about why we expressed libraries as `require "-luserlib";` rather than, say, `require "userlib.a";`, I think it came down to wanting to avoid...

@psath : It took me awhile to get back to this, but I've made some changes taking inspiration from your suggestion above and think we're in a strictly better place...

Thanks for taking the time to capture this, and for the extensive write-up, @twesterhout!

@twesterhout : I wanted to make sure you were aware that https://github.com/chapel-lang/chapel/pull/24746 should have addressed your first of two requests here. If you get a chance to try it out...

Cool!