Nim is a compiled, garbage-collected systems programming language which has an excellent productivity/performance ratio. Nim's design focuses on efficiency, expressiveness, elegance (in the order of priority).
Yea you are correct they would normally be named differently.
In this case however it's more like versioned inheritance
In this case however it's more like versioned inheritance
Dog
Dog # (V2)type
Dog = object
age: int
# Another file (V2)
Dog = object of first_file.Dog
weight: int
embed the version in the type, then alias the versioned type into a "regularly named" type?
v1 in a v1 module, etc
then in some "all types" module
then in some "all types" module
type Thing = ThingV7 or so
export it too sorry
Hmm, so then you're doing
all_types.Thing | all_types.Thing2
i dont really know what your versioning use case is
The versioned use case is the beacon chain, and supporting older versions of validator systems
Sorry to be less specific, a crypto use case in a format like git branching
how will you know which TypeA you want to return?
1 reply
If you're happy to do this: something[test_a]() -> test_a.TypeA , then what about
something[test_a.TypeA]() -> test_a.TypeA ?
1 reply
It's interesting what you're trying to do, but I don't think I grasp what makes one of the types in the module special to become the return type. It sounds like it's purely based off the type name?
import macros
import "."/[test_a, test_b]
macro something(kind: untyped) =
quote do:
`kind`.Type(data: 5)
echo something(test_a)
echo something(test_b)Error: expression 'test_a.Type(data: 5)' is of type 'Type' and has to be used (or discarded)
Is there some easily spottable problem with the above code?
I'm only just trying to write my own macros 🥲
But it looks like that's a function with no return
import macros
import "."/[test_a, test_b]
macro something(kind: untyped): untyped =
quote do:
`kind`.Type(data: 5)
echo something(test_a)
echo something(test_b)
Result
(data: 5)
(data: 5)
Thank you guys, very helpful 🙏
🦆 , no worries 🙂 was an interesting question
Is there something in the standard libs to get the screen resolution?
hm that might be something you would have to get from wayland/x on linux, and from win32 api on windows
(just guessing)
for windows probably this https://stackoverflow.com/questions/4631292/how-to-detect-the-current-screen-resolution
Don't think so, unfortunately
I implemented something like this for notifishower, you're free to grab the code for x11 from there if you want to make a library out of it :)
I mean you can't do screen resolution without handling multi-monitor setups
notifishower does that, it creates and updates a list of monitors
Compiling C:\Users\jos\dev\tfp\labs\crag\tests\test_scanner (from package crag) using c backend
fatal.nim(53) sysFatal
Error: unhandled exception: index 3 not in 0 .. 2 [IndexDefect]
Tip: 3 messages have been suppressed, use --verbose to show them.
Error: Execution failed with exit code 1
... Command: C:\Users\jos\.nimble\bin\nim.exe c --noNimblePath -d:NimblePkgVersion=0.1.0 --path:C:\Users\jos\.nimble\pkgs\patty-0.3.4 --hints:off -r --path:. C:\Users\jos\dev\tfp\labs\crag\tests\test_scanner
it doesn't matter what's inside my test file
i always get this error
i have no clue how to debug this, is there a way to get a full stack trace?
1 reply
ok well I think it's missing the .nim in the cli command listed at the bottom, which might make sense?
idk why it would, or if it's supposed to
at least it should be
if you want to get the compiler stack trace, you need to build the compiler in debug mode