> The conference time (or at least timezone to get an idea) is rather important
> because depending on your timezone the conference could effectively be on
> another date.
The registration form currently says: _Proposed start at 11 a.m. UTC_.
That should give you a rough idea about when can
compile OS is Debian 10.4 x86_64 # nim --version Nim Compiler Version 1.2.0
[Linux: amd64] Compiled at 2020-04-03 Copyright (c) 2006-2020 by Andreas Rumpf
git hash: 7e83adff84be5d0c401a213eccb61e321a3fb1ff active boot switches:
-d:release
# cat hello.nim echo "Hello World"
# nim -d:release
Have you read [Internals of the Nim
Compiler](https://nim-lang.org/docs/intern.html)?
This is just a simple question. I have started looking at the nim compiler
source and trying to implement my own backend for nim. Is there not
documentation for the nim compiler or is it reserved for developers? I might
just not have found where it is though.
Also, it'd be cool to see how many standard Nim libraries on threads could be
extended to the ESP32 as well. That's far down the list, but how would one
integrate vTasks*** with Nim?
Hey all! I'm experimenting with an OS port for FreeRTOS, similar to that for
the Nintendo Switch. Currently I'm focusing on the esp-idf (esp32) which
includes LwIP. Essentially so far it's posix.nim with all the non-FreeRTOS
parts removed (probably 80% of it). Importantly, there's a couple of
> 5\. Always put your code into a src dir. Even though nimble supports not
> having src dir, it’s just better in every way.
In my experience that's the best way to break your project because on install
nimble removes the `src` directory and then all your paths are wrong.
This is so broken that
For machine learning in particular deep learning this is how I do it:
1\. I use inheritance, but only to be able to store the objects in the same
container, **never for dispatch**. Example on neural network layer, called
`Gate`, re-using the terminology from Andrej Karpathy's [Hacker's Guide to
# console.nim
when defined(windows):
import system/widestrs
proc setMode(fd: int, mode: int): int
{.importc: "_setmode", header: "io.h".}
proc fgetws(str: WideCString, numChars: int, stream: File): bool
{.importc, header: "stdio.h".}
Personally, I never streamed a talk yet, so I'd be quite interested in the
technological side and what preparations I'd have to do; ideally also some
hints how to test this beforehand. I just learnt about OBS from the above post,
sounds interesting, but will definitely want to have the tech
nimby?
nimpish?
> 5\. Always put your code into a src dir. Even though nimble supports not
> having src dir, it’s just better in every way.
What's the difference between putting my source code files into a `src` folder
instead of putting them into my root folder? I'm not so familiar with nimble,
but isn't
It seems to be a problem with Godbolt itself as far as I can see - it prepends
these arguments for compilation (so it outputs assembly and not the binary)
-o:/tmp/compiler-explorer-compiler2020416-1360-d68wkg.sqfva/output.s
--nolinking
Thank you both! Indeed, I simply wrote
= pathsplit.tail.replace(re"^[\!\+\-]+\s", "")
Run
without importing any regexp library explicitly, and it works fine.
14 matches
Mail list logo
