> “Data” is not the plural of “anecdote.”
I love it. :-)
@mratsim I have some news about the drawbacks you mentionned
I have been working hard to address some issues in my NimGo library. I have
implemented custom stacktrace management in debug mode to allow for better
debugging: In case of a raise, it is possible to see in a nested way where the
erro
Awesome video editing and presenting skills :)
Just finished working on a video demonstrating how to set up a new/existing
Unreal Engine 5 project with NimForUE plugin. It covers:
* Installing Nim devel
* Converting blueprint-only project to C++
* Adding NimForUE to C++ project
* Setting up VSCode
* Testing
[Installing NimFor UE
Declarations will look like:
type
Either[T, E] = case
of Le: T
of Ri: E
Option[T] = case
of Some: T
of None: discard
IfTree = object
condition, thenPart, elsePart: Tree
ProcTree = object
fn:
Teholääkkeen Natures Garden CBD on tarkoitus tarjota hauskempaa makuuhuoneessa.
Ottamalla tuotetta miesten sanotaan pystyvän palauttamaan seksuaalisen
suorituskykynsä. Natures Garden CBD Tosiasia on, että monet miehet tuntevat
olonsa rajoittuneiksi makuuhuoneessa ja heidän itseluottamuksensa kär
Is the final syntax described somewhere?
Thanks!
The next best thing in my opinion would be to add a NimGo-aware Channels. You
would use NimGo in your main thread doing some I/O stuff and when there is a
complex calculations, you transfer communicate with an OS thread. Or if you
know you have to handle a lot of I/O, you can use multiple thread
As a test, I exported a procedure via `{.exportc,dynlib.}` without saving my
objects in a `Table`, and let my `FFI` library handle it, and I have the same
memory size.
In conclusion, I think I'm on the right way (I think !). Another solution would
be to destroy the elements in my table as soon
