Hello `nph`, an opinionated source code formatter for Nim

sounds like an excellent PR opportunity ;)

Nim Tooling Roadmap

I'm glad tooling is being worked on in whatever capacity the contributors see fit. It's their time/money after all. I probably should have refrained from disrupting this post with my otherwise healthy and natural reaction to Microsoft and their buggy, slow, and bloated Trapware.

Is it possible to safely share refs across threads?

> Also, wise people have suggested that rather than making the algorithm more > complex, turn it into a cycle/leak detector and embrace (atomic)ARC as it > simply is a better fit for modern Nim. And I agree. There's definitely some benefits to that approach. Though wouldn't the cycle detector s

Nim Tooling Roadmap

> Hm, I'd have seen this more as a move of status contributing since in my head > they're both (the status-org and the nim-org) very separate entities. However > I guess who belongs to what group and if that's a meaningful distinction is > sufficiently intransparent to me as a someone not workin

Is it possible to safely share refs across threads?

> Good point. But you cannot have race conditions on dead subgraphs (they are > dead!), so if you reliably collect in one pass it should be possible. The pain point was on shared parts of the graph, where one side was dead but the other side had a live root. If you had two algo's running concurr

Hello `nph`, an opinionated source code formatter for Nim

glob expansions do not work that well on windows, and you cannot easily do recursive glob expansions.

Hello `nph`, an opinionated source code formatter for Nim

> but why? *.nim / "find" / etc... To encourage the ecosystem to use it. Setting up find or globs adds an extra step to be done. I think we see this with doc generation as well where there's not a default `nimble docs` for project docs (and version tagging as well). So it'll often be skipped.

Nim Tooling Roadmap

This is awesome! Thanks a lot to status for their continued support of the nim community! This is a very exciting plan (integrated REPL! Better debugger!) but I have a few questions and comments: * I would recommend changing the description of the nim extension to clearly state that it is th

Hello `nph`, an opinionated source code formatter for Nim

> It'd be nice if it could run on a folder, or perhaps a Nimble project. What’s wrong with just using glob expansion for that?

Nim Tooling Roadmap

Hm, I'd have seen this more as a move of status contributing since in my head they're both very separate entities, but I guess who belongs to what group and if that's a meaningful distinction is sufficiently intransparent to me as a someone not working on any of the core-stuff that I'll happily

Nim Tooling Roadmap

I don't think you're correct here: > Note that this is not a nim action, this is status doing those actions which > benefits the wider nim ecosystem. The first post clearly says "The official Nim extension for VSCode", and it's also sitting under the nim-lang org, which (I think) makes it an of

Smart Hemp Gummies Australia:- official Website, Order And Best Product.

Smart Hemp Gummies Australia:- Now we have come to the main question that many of you are looking for and this is whether the supplement is legit or not. Taking all of these that we have about Smart Hemp Gummies Australia, it is apparent that the formula isn’t legit. Facebook @

Nim Tooling Roadmap

Note that this is not a _nim_ action, this is _status_ doing those actions which benefits the wider nim ecosystem. Personally I'm happy for any improvements they shell out, anything to make my life easier while I write my threads-as-a-backend-server-for-applications library ^^

cannot open: /dev/stderr

> I wonder why it fails writing to stderr. its even more of a head scratcher how it can write the exception to stderr after it couldnt write to stderr

Nim Tooling Roadmap

You can use every "official Microsoft store" extension/plugin in VsCodium too, but you need to download the .vsix file and the import it manually in the menu of VsCodium

Hello `nph`, an opinionated source code formatter for Nim

I tried this new version and it's a good improvement. However, it turned this: when false: let axis = parseInt(paramStr(1)) let ph = arange(0, 60*5, 5).reshape([3,4,5]) echo unwrap(ph, axis=axis, period=6) # echo diff(ph, axis=axis) # echo &"{ph=}"

cannot open: /dev/stderr

Excellent thanks for catching that. I did some research and found this: try: writeFile(filename, text) except Exception as e: echo e.msg Run I'm try it and see what happens, because it seems more robust for any type of Exception, future proof. If

Nim Tooling Roadmap

I begrudgingly use vscodium and the _official nim extension_ doesn't show up for me. I would prefer an up-to-date, fairly basic gtk editor written in nim and will eventually try to write one if nobody else beats me to it. Being expected to get official nim tooling from the **Microsoft Store** is

Why Choose Smart Hemp Gummies Australia ?

Smart Hemp Gummies Australia:- takes transparency seriously. All their products undergo rigorous third-party lab testing to verify their potency and safety. This ensures that you're getting a reliable and high-quality Smart Hemp Gummies Australia product. Facebook @

Is it possible to safely share refs across threads?

> cycle/leak detector and embrace ARC Very interesting, would be nice to have a "cycle detector API".

Hello `nph`, an opinionated source code formatter for Nim

[Vertical spacing](https://github.com/arnetheduck/nph/pull/10) update: semi-retained, per feedback - black indeed does something similar. Compiler: > It'd be nice if it could run on a folder but why? `*.nim` /

Package-Rot as growth hindrance

\-- Size of the package is not necessarily relevant to whether something needs updating or not. -- stuff like proprietarySaasFeature (aka GH stars) should definitely be excludable by users. -- whether the package has releases/versions at all is good to know. `--whether those versions are 1.0+ i

Nim Tooling Roadmap

The idea in general is to implement the features as extension agnostic as possible.

Nim Tooling Roadmap

Very good news for the Nim ecosystem indeed. After the 3th survey complaining about the lack of/not fully supported/not frequently updated tools seem like something is finally moving forward Congrats jmgomez, nickysn

Nim program crashes when using recursivity and openarray

using `[..]` creates a seq[char] from your openArray, so your function uses O(n^2) memory and is possibly being killed by the os. instead of using `..` use `recursiveExplorer(toOpenArray(s,0,s.len-2))` and you wont produce a copy

Nim Tooling Roadmap

Will the VSCode points be actually specific to the extension or is the plan to improve ‘nim-lang/langserver’ for this? Really hoping for the latter as that would make these improvements available to everyone instead of just vscode users

Nim program crashes when using recursivity and openarray

The following Nim program crashes and I don't understand why: proc recursiveExplorer(s: openarray[char]) = if s.len == 0: return # processing(s[^1]) recursiveExplorer(s[ 0 ..< (s.len-1)]) var data = readFile("someLargeFile.txt") var conver

Nim Tooling Roadmap

great news!

Nim Tooling Roadmap

This is such great news to have you work on this and getting paid for it :) I have no meaninful feedback to give, but I'm looking forward to see the impact of it !

Nim Tooling Roadmap

We're pleased to share some updates regarding the Nim tooling ecosystem. As part of ongoing efforts to enhance the Nim programming experience, Status has brought on board part time @nickysn and myself specifically to focus on Nim tooling development. Our task is to streamline and improve the too

Hello `nph`, an opinionated source code formatter for Nim

I like the idea. Just tried it on a few files on my project, so here is some feedback: 1. I think the 88 character limit is way to low. Personally my requirement for the character limit is that I can view two files next to each other (mainly for diffing), and I can easily fit up to 140 charac

Brackets and unary operators

You need to use additional brackets. (($input.type).toUpper)