I'm not against Ruby neither against jzakiya... I'll also admit that one of the
first thing I wrote in nim was the `...` iterator with that precise semantic (I
also think that a better choice would have been to make the `...` iterator
count until end-1 since that is what you need 99% of the
@jzakiya Could you please share the code you used for benchmarks?
There's absolutely no sense in badmouthing Ruby syntax. I'm not a fan of Ruby
myself, I don't like its syntax, but calling it ugly and even comparing it to
Brainfuck is a bit too much...
I'm afraid, the natural reaction for @jzakiya after those replies will be to
become defensive and quit the
@jzakiya It's best you share the code you used to reproduce this behaviour for
further examination. I'm no expert on Nim's internals, but apparently
..<
is exactly the same as
-1
in terms of generated code, so that may be why Araq is so skeptical about your
The intent of the post was to provide information **from a user's perspective**
with real world code on how to make Nim better _from the user's perspective_.
Why did you make the assumption I didn't compile my code with `--d:release`? I
did. What I hoped you appreciated was that using fixed
Maybe compile with `-d:release` the next time. There are no plans to deprecate
`..<` only to deprecate `<`. What's confusing about `..<` anyway? That Python
lacks it? But Swift has it too.
> In Ruby a..b is used to include from a to b whereas a...b is the equivalent
> of a..b-1.
Yeah but it
Hi perturbation2! I have not had much time to work on Neo lately, but there is
a [list of issues](https://github.com/unicredit/neo/issues) which I use to
track features that I had planned to add. Most should be rather self contained.
If you want to contribute, I will be glad to help
@LeuGim, @coffeepot: Thanks so much for your guidance. I'm an idiot - you were
right the indentation was the issue.
@coffeepot: thanks so much for a really useful library.
Try this:
type
ValueSpan = tuple[v0, v1: int]
ValueSpanSeq = seq[ValueSpan]
ValueSpanList* = ref object
descr: string
vsl: ValueSpanSeq
{.this:self.}
proc newValueSpanList*(descr: string): ValueSpanList =
ValueSpanList(descr:
@Ar Thanks! Being new to nim and trying to learn it by doing simple
things, I tended to consider templates as a rather advanced feature to master
"later", but you demonstrated that they can be pretty useful from the very
beginning
@mratsim No, it's not a silly question. It did not
Maybe a silly question but why don't you use Nim default Slice objects?
11 matches
Mail list logo
