> Virtual functions implemented
Sweet. (Un)fortunately you got it to work without a Nim compiler codegen patch.
;-)
How did you do it?
Yes, I am using `uing`. I wasn't (still am) not sure whether the libraries are
not properly configured, or it's a configuration issue on my side. It happened
for two libraries, so I'm thinking that my setup is somehow broken.
It's just so odd, because the library config files do specify the link
> I am also reticent to use Natural types, since you can not convert back and
> forth with integers and most functions are written for integers in libraries.
Not true?
let a: int = 1
let b: Natural = a
let c: int = b
echo (a, b, c)
Run
The problem might be
yes, we are close to be "feature complete" hopefully in the future it may
attract people into the Nim
> To me, this additional type add «color» to the functions just like
> async/await construct does in Javascript
Every type distinction introduces these "colors". So it doesn't actually mean
anything to complain about "colored" functions.
This is probably linked to exercism.io proposing a challenge: learn a subset of
these mechanical languages challenge with Nim being in there.
People are doing a lot of Google queries to learn the language, thus making our
position in the TIOBE index climb.
When we know Nim, it is unuseful to lo
>From a computer algebra point of view, I still find `uint` more interesting
>than `Natural` types. There are some algorithms for reduction modulo p, where
>you actually want the overflow to happen. You can sometimes detect it
>mathematically speaking and correct the overflow for higher performa
Nope, I don't know the deadline for 2.0.
To add to the previous comments, if by unsigned you really mean positive, use
Positive or Natural types. Then you'll have your checks, both for positivity
and overflow.
Thanks! Was exactly this! Now works!
Nim's unsigned ints do not model integers. They model integers modulo 2^width.
As such, the results are accurate.
11 matches
Mail list logo
