If these test cases are representative of what the code would actual run on,
then these suggestions are fine. If you can have arbitrarily long strings
though, you should pull phrase.strip out into a variable, since it's linear
time and you're running it twice on nonempty input and checking equal
Hey all, I've been exploring moving some of my analysis work over to Nim.
Currently I use
[Polars](https://docs.pola.rs/user-guide/transformations/time-series/parsing/)
for my df with python bindings. It has a decent story around DateTime handling
in ingestion, transformations, grouping, etc.
What's are the favored Nim postgres libraries?
No Nim microservices discussion is complete without a mention of
[Mummy](https://github.com/guzba/mummy)!
Congratulations on making the front page of Hacker News! Always nice to see a
Nim project get some attention.
A good first step is to check [Nimble](https://nimble.directory) to see if
anyone has made libraries to simplify this. There appear to be several for AWS
and OpenAPI.
Good talk, lot's of passion!
For companies that use Nim, Reddit comes to mind, even if it it's just
Treeform. He's a one-man army.
"3-5 years"
GenAI is not a solution generator, it's a reduce-the-solution-search-space
tool. I've seen you opine on the doom of "human programming" before; I wish you
were less concerned and still making investments into the ecosystem. Mono was
amazing.
Just so we're clear here [TIOBE lists Scratch at
16th](https://www.tiobe.com/tiobe-index/).
I think we need to go after the children.
On topic: Checkout HappyX
As an aside out of curiosity, how do you hope people receive your message when
you present yourself as "throwaway567843"?
Okay gotcha, so the RFC repo answers the title question (there's an candidate
for v2 tag)
In the lifecycle of an RFC does "accepted" mean implementing this has been
added to a backlog somewhere or that it's a topic that is open for community
input?
A few days ago, I encountered frustrating behavior with hashset where hash is
not defined for arbitrary ref objects, which as [pointed out by Araq a few
years ago](https://forum.nim-lang.org/t/7765#49360) (pre 2.0) is "a strange
omission". The functionality has since been added behind a compiler
That was a good read. Do you have any more articles you can point me to that
explain your design choice of using exceptions rather than monads or even
fancier concepts? Is it largely the performance benefits you've argued for here?
I've found exceptions to be problematic from a spooky-action at
So is the fork (nim-lang/vscode-nim) the recommended one or the forked
(saem/vscode-nim)?
The former hasn't been published to the extension marketplace. The latter
hasn't seen a release in a year and a half.
It does. It doesn't work with nimlsp.
I'm not clear what you're talking about `f(param=arg)` is syntax for a default
argument. Do you mean `f(arg:type)`?
I'm mostly used to it from Kotlin and Rust where in both cases you have to
specify function signatures, so it's not really an issue for callers. I suppose
if you don't have hints,
Oh sweet! Looks like it's on it's way to
[VSCode](https://github.com/saem/vscode-nim/pull/134) as well.
Hey thank you for taking a look at this!
I owe you an apology. I read the article a couple days ago, then came back to
it last night just before falling asleep and, blithely ignoring all the text,
C&P'ed my way into the problem.
It for sure still works. You just have to, you know, read it...
H
Hi all,
I just discovered Nim and have been going some of the blog articles. I read
"[Benchmarking the
Beast](https://nim-lang.org/blog/2021/07/28/Nim-Efficient-Expressive-Elegant-Benchmarking.html)"
which is an awesome demonstration of Nim's features. I tried to run it with
Nim 2.0.0_1 and th
19 matches
Mail list logo
