Mirror of forum.nim-lang.org

6900 :: Any attempts at implementing filestream and std lib friends on NodeJs?

• saem (orginal) [2020-10-08T09:07:45+02:00] view original

  Just wondering if anyone made any headway in this area or has stumbled upon some work that I might be able to reuse?

  I've been searching for any work that provides equivalent APIs for IO and all that fun stuff, so far no luck. I've found a few github issues and rejected pull requests that are somewhat relevant but nothing concrete. It'll make life a fair bit easier for the vscode extension. Thanks in advance

---

• Araq (orginal) [2020-10-08T11:19:37+02:00] view original

  Please read https://github.com/nim-lang/Nim/pull/15475 for the pros and cons. Unfortunately this is not yet an RFC. And I think we all agree that supporting a new target should be justified in an RFC.

---

• saem (orginal) [2020-10-11T19:10:41+02:00] view original

  Thanks for the link, @Araq -- I think I missed that one when I was reading a number of Nim + Node related posts.

  I actually agree with not including nodejs in the core as it's more work and I'm not convinced the right abstractions are in place to really make this work well just yet. I'm noodling on the RFC, there are a bunch of intuitions I've developed around being exposed to this in Haxe but it's not a set of principles that I'd feel comfortable driving an RFC -- I can post what I have here or elsewhere for interested parties

  Mostly, I'm trying to collect various work in this space to get a shim for the VS Code extension that provides a stdlib look alike API. Either it already exists, is in a few pieces, various states of functioning, or some combination thereof.

  The ultimate purpose is to make it easier to extract functionality from here and into language servers and other tools as that's where much of this core functionality belongs, the extensionn should be mostly concerned with the interface (reporting, visualization, commands, orchestration, etc...).

  I'm not sure VS Code is the right thing long term for Nim and I don't want all that good stuff locked behind it too firmly. Heck, someone might want to make a pure browser version and/or use a bunch of it in a desktop or other version and I don't want to make it too hard for them in the long term. Better yet, there might be slices of capabilities that someone finds useful that they want to leverage elsewhere.

  I'll update my original post with a "manifest" of what I've found and as people turn more tidbits in perhaps that can form a catalog of all this type of work in Nim land.

---