I had the hope that someone would see the solution immediately. Testing (Linux)
is possible with only a few commands of course, as we have a nimble package:
cd /tmp
git clone https://github.com/stefansalewski/gintro
cd gintro
nimble prepare
nimble install
But I
In this case a smaller example to reproduce the issue would be nice.
You are right that I do it at compile time only. Delegating the choice at
runtime could really complicate things especially with vectorized data layout,
and it is unnecessary for me to maintain binary compatibility since I have
chips of power, xeon, nvidia gpus to worry about. To minimize perfor
I have just shipped v0.2 of package gintro. Its connect macro can now deal with
arbitrary number of arguments, which is needed for a few callbacks like the
"draw" callback for DrawingArea widget. (Additional, module gtksourceview is
now included, as well as a preliminary version of full cairo dr
Regarding a table of what editors can do with regard to Nim integration, see
here:
[https://github.com/nim-lang/Nim/wiki/Editor-Support](https://github.com/nim-lang/Nim/wiki/Editor-Support)
As this is a GitHub wiki, anybody can feel free to update and ammend the entry
with any other plugins/edi
> "let's have a simple core but metaprogramming"
>
> I like that, a lot!
Yeah, I have been programming for about a year, and messed around with a few
languages (C# and Python mostly), then fell in love with C due to its
simplicity. Unfortunately, that simplicity made some things a pain to do (f
Evangelism makes people grow heated, like a gamble, making all other goals
secondary to spreading out over the world. "_What's the difference what a
language Nim will be, let it just be the most widespread!_", "_For what target
audience can Nim be promoted? Let's turn it into a language suited f
> "let's have a simple core but metaprogramming"
I like that, a lot!
I don't care about Ada either
What I would like is a language that is expressive and as simple as possible -
I hope that the C / C++ "backend" will stay - and Nim is that, to me.
I don't need any more selling points, to be
jxy - I did look at that, and perhaps I am reading the code wrong but I think
that one does compile time decision about which SIMD feature set is available,
not runtime, is that correct?
I'm looking to be able to build one exe, send it to a computer with SSE or AVX
or AVX512 and have it use the
As replied in your other thread, the simd stuff wrapped under
[https://github.com/jcosborn/qex/blob/devel/src/simd.nim](https://github.com/jcosborn/qex/blob/devel/src/simd.nim)
is quite complete. You may need a couple of files in that directory to get it
to work. If there is sufficient interests
> In order to turn it into a fruitful discussion: What feature should we
> **remove** from Nim?
`method` at least, once `vtref` and the like have landed.
> Nim is a simplistic systems programming language with an AST based macro
> system on top of that.
Why simplistic? IMO it's fairly rich, bu
Good suggestion. Thanks. What are the functionalities would you like to see in
the optimization library?
Oh so it's about Nim v1.0 again. I wanted to release that years ago but the
community talked me out of it. _Shrug_, sometimes the community is just wrong.
> I didn't mean that Nim has a "zillion unfocused ideas" (it's not a real
> number and a general point about business plans), but the top ex
Will you publish the optimization part, which is obviously not tightly bounded
to the purpose of the framework, separately? It would enable people to easily
build other science libraries, which can lead to this optimization library
having more contributors, which will probably be good for your f
Dude, you are over-complicating things!
In the last 9 months, what happened?
Well, I got interested in Nim, that happened, and I guess a lot of other people
did try Nim out as well, seeing that C and C-like languages (Odin, Jai, .. ) is
seeing a revival. Perhaps because of C++ fatigue? Back to
@LeuGim
I think it is partially my lack of understanding. The documentation around
arrays is not as clear as it could be around the ways to initialize and
populate arrays.
Yes, large arrays are difficult to initialize or fill by literal. Though the
core devs seem to be taking steps to fix this
I am not bashing Nim; I am speculating about what (IMHO) it could be doing
better. Key word: **_focus_**.
This thread is about summing up the last 9 months, and my humble summation is
that, as far as I can tell, things haven't moved much. Is Nim marching steadily
towards reasonable version 1.0
17 matches
Mail list logo
