newProc macro question

It makes your example to work. But you'll also lose the ability of getting the type information from the input, by using an `untyped` parameter. Another way is to take a typed parameter and make a recursive copy of it, replacing every node of the kind of `nnkSym` with that of `nnkIdent`. But I

can't run nim

Known problem, complain to your AV vendor. [The same issue](https://forum.nim-lang.org/t/10824) was last reported three days ago. Basically your AV vendor sucks at fingerprinting Nim binaries and just thinks anything written in Nim is a virus.

Wishlist: Ideal UI library for Nim

I'm sorry about the possible offence. But you did post the same links on a different thread too, which is fine.

newProc macro question

Is that seriously all I had to do... thanks guys.

can't run nim

Antivirus software blocked this

`nph` opinionated formatter v0.3

> Error: Unsatisfied dependency: nim (2.0.0) 👑 v2.0.2

Wishlist: Ideal UI library for Nim

Hello. I am aware that people like you have a high degree of interest in having someone else's inspiration correspond to you satisfactorily about how you want things to go. However, please be in no doubt that our contributions are made with professional nobility and with the intention to help.

Nim Tooling Roadmap

> I would prefer an up-to-date, fairly basic gtk editor written in nim and will > eventually try to write one if nobody else beats me to it. Like the old Aporia?

Nim Tooling Roadmap

> You can use every "official Microsoft store" extension/plugin in VsCodium > too, but you need to download the .vsix file and the import it manually in > the menu of VsCodium But there is a serious problem on discoverability. Why would a VSCodium user do that if when he searches for nim extens

#pragma pack(push, n) equivalent for Nim Objects

Ok I think the following compiles and works as expected. type TestObj {.packed.} = object m_1 {.align(8).} : int64 m2 {.align(8).}: float64 m3 {.align(8).}: uint8 Run It would be great if we could set the alignment for all object fi

Nim v2: what would you change?

I mean that var fooBar = 12 echo foo_bar echo foobar Run will not compile with --styleCheck:error option. As always, having fooBar, foo_bar and foobar be 3 different things is a huge code smell and will eventually cause problem in a code base.

`nph` opinionated formatter v0.3

`nph` 0.3 is out! Binaries from the [release page](https://github.com/arnetheduck/nph/releases) * Back to `,` as parameter separator - this helps compatibility with inline procs due to a parsing quirk where `;` gets eaten by the inline parser while `,` (mostly) does not * New manual at

Sum types, 2024 variant

It makes obsolete and builds upon

Sum types, 2024 variant

Is this related to RFC #368 and/or #525 ?

Bliss Rise CBD Gummies {How To Buy An!} Reviews and Price..

┈➤╰┈➤ Item Name: — Bliss Rise CBD Gummies ┈➤╰┈➤ Utilized For: — Reduces Pain, Stress, Anxiety And Sale Now.. ┈➤╰┈➤ Composition ➥ Natural Organic Compound ┈➤╰┈➤ Incidental effects: — NA ┈➤╰┈➤ Rating:— Overall rating: — ☆ (4.5/5.0) ┈➤╰┈➤ Availability ➥ Online ┈➤╰┈➤ Where to Buy ➺ {Buy Now Here

Nim v2: what would you change?

Do you mean the flag `--styleCheck:usages` here?

#pragma pack(push, n) equivalent for Nim Objects

Thanks for your reply. I don't necessarily need them always tightly packed, but with a byte boundary. The 'n' byte part in the C pragma compiler directive. Is it possible to do like this? I tried but it doesn't seem to compile. type TestObj {.packed(8).} = object m_1

newProc macro question

For ratchet on what that does: It tells nim to not really try to make sense of whatever code gets put into the `mkCaster` macro. So you are allowed to have entirely invalid stuff in there, you just need to create NimNodes that contains valid code as the macro output (which you do). By using pr

newProc macro question

Replacing `proc` with `untyped` will fix it. macro mkCaster(caster: untyped) Run It seems that all the symbols were bound to somewhere before passed into the macro, as a side effect of using typed parameter. The compile thus thought you were capturing outter variables

Nim v2: what would you change?

An idea: Within your config.nims, maybe implement a macro within something like: when defined(forceCaseSensitivity): # do stuff Run This macro could maybe loop through your project's non-stdlib and non-nimble modules, building a registry of identifiers and whe

Nim v2: what would you change?

You can treat case insensitivity as error using compiler option so I don't understand how it can be the only blocking point.

Nim v2: what would you change?

You sacrifice more for style insensitivity than the entirety of Rust ?

how to get pragma of the field in macro?

I don’t understand the role of `getTypeImpl`, it even can not get the type name (e.g. A)

how to get pragma of the field in macro?

thanks a lot ;-)

how to get pragma of the field in macro?

You can use `getTypeInst` combined with `getImpl` to get the type's AST including pragmas on its fields, that's how `hasCustomPragma` does it (but as a macro it can't be used from inside a macro AFAIK), see `customPragmaNode` in

Nim v2: what would you change?

There are many C libraries with `Foo`, `foo`, and `FOO`. I learned long ago how to rename in a wrapper. I can make Nim work for personal projects. But the problem is when I am trying to convince a team to adopt Nim. This single impediment ends all discussion. I work at a Mag7 company on embedde

how to get pragma of the field in macro?

i try to use `fieldPairs()`, but unfortunately macro parse(a: typed; k: untyped): untyped = result = nnkCaseStmt.newTree(k) for fk, fv in a.fieldPairs(): when fv.hasCustomPragma(opt): result.add nnkOfBranch.newTree( newLit(fk), nnkStmtList.n

newProc macro question

Hey, I'm trying to implement a macro to reduce some cumbersome boilerplate code. However, I can't seem to get `newProc` to work. Here's the stripped down macro code: import std/macros macro mkCaster(caster: proc) = expectKind(caster, nnkLambda) echo

Niklaus Wirth has died

there is a very nice and long interview here (from 4 years ago): Would be very much interested in understanding more on how his work impacted Nim, I never studied Wirth's work, I only know what is generic knowledge acquired through following Nim. Fr

MycoSoothe Reviews: What Users Are Saying About Nail Health

┈➤╰┈➤ Product Name ➥ MycoSoothe ┈➤╰┈➤ Main Benefits ➥ Nail Fungus Fights Against Skin & Nail Health Supplement ┈➤╰┈➤ Composition ➥ Natural Organic Compound ┈➤╰┈➤ Side-Effects ➥ NA ┈➤╰┈➤ Rating ➥ ┈➤╰┈➤ Availability ➥ Online ┈➤╰┈➤ Where to Buy ➺ {Buy Now Here — Click Here} Official Website@Offici

how to get pragma of the field in macro?

i found `getTypeImpl` can not get pragma info ;-( > > static: > echo A.getTypeImpl().treeRepr() > > > Run result is: ObjectTy Empty Empty RecList IdentDefs Sym "name" Sym "string" Empty IdentDe

how to get pragma of the field in macro?

Thanks for your advice ;-) i modified code and got error as below: macro parse(a: typed; k: untyped): untyped = result = nnkCaseStmt.newTree(k) for fieldDef in a.getTypeImpl()[2]: let fieldNameIdent = fieldDef[0][0] # error: Expected one of {nnkSym, nnkTyp

how to get pragma of the field in macro?

https://nim-lang.org/docs/macros.html#hasCustomPragma.m%2Ctyped%2C

Sum types, 2024 variant

I can see how `None` could easily behave like `nil` but `Le[string, _]` is a new beast ("partially instantiated generic").

how to get pragma of the field in macro?

template opt() {.pragma.} type A = object name {.opt.}: string age: int var a = A(name: "foo", age: 10) # expect like below: # # case k # of "name": # a.name = "🤔" # else: # discard # # but result is: # # case k

Sum types, 2024 variant

This becomes even more obvious when you look at `Option[T]` \- `None` for `Option` doesn't know/care about `T` \- when you construct a `None` you don't have to provide a value for the "some" side - why would you have to provide its type? It's completely irrelevant for the none side (see

Sum types, 2024 variant

> Wait ... what? That looks like the kind of feature that saves a couple of key > strokes for the end user No, this is actually quite an important feature! Imagine a function constructing an error return for `Either` \- consider `return Either.Le(42)` \- there is no need to repeat the full eith

Maybe nappgui is best cross platform gui lib for nim

>I'm over the native GUI thing for a few reasons: * An App Gui should be targeted at the task on hand. Not the OS. Think 3D modellers, FocusWriter, GohstWriter, DAWs and DAW plug ins, CAD. Old school music trackers. etc. * Native may waste screen estate that, despite the current monitor size

Sum types, 2024 variant

> I can construct the Either knowing only one of A and B - from the example, > Either.Le(42, false) must be implicitly convertible to Either(bool, _) with > the B left unspecified at the instantiation point - this is an important > feature! Wait ... what? That looks like the kind of feature tha

Maybe nappgui is best cross platform gui lib for nim

The largest browser in the world does what I'm describing with much success. On the other hand, Firefox used to be more styled toward the operating system, and has also moved away from that. Even then, its default widgets are styled like the system, which has led to inconsistent and annoying sty

Niklaus Wirth has died

Rest in peace, Niklaus Wirth. :-/