Which VSCode plugin do you recommend?

I'm unaware if you resolved this problem already, but for people who were looking to diagnose this `could not load: pcre64.dll` issue and have installed nim from scoop like me, add `"$(scoop prefix nim)\bin"` to your `Path` variable. The manifest doesn't do this by default (though there's an iss

Releasing Constantine v0.1.0 - A modular cryptography stack for blockchain and proof systems

# 👏👏👏 🗝️

Questions on the current stage of concepts

Generic procedures are just splendid, this seems to be a bug that it fails to validate that it's possible to instantiate the generic after sem checking type Addable = concept c, type T c + c is T Coll = concept c typeof(c.items) Addable

Questions on the current stage of concepts

Thanks for the feedback. I tried {.explain.}, but it didn't seem to do anything. I've been looking for a programming language with this weird/arbitrary combination of features: 1. Good support for functional programming, or enough flexibility/abstraction that you can implement functional prog

Questions on the current stage of concepts

Thanks for the suggestion. I tried this out, and although it works, AddableColl appears to end up being identical to Coll, rather than incorporating the additional "Addable" constraint. For example, it allows you to calls @["0", "1", "2"].sum, and you only get the error inside the function when

Questions on the current stage of concepts

Even though new concepts exist I find they have many jagged edges as they're a even less used than their old style counterparts. I imagine the `proc +(a, b: T): T` is the problem here but I did not check. A working implementation that uses the new style concepts is the following. t

Questions on the current stage of concepts

Quoting myself on July 1st: > And I think it's quite important to document and give examples of "new > concepts" > If we want to have > a strong ecosystem that

Nimble incorrect package structure warning: What is going to be?

Done,

Nimble incorrect package structure warning: What is going to be?

> If not, do you accept PRs to remove it? Oh god yes! Bring it on!

Nimble incorrect package structure warning: What is going to be?

Nop that warning should disappear. I've said so countless times on the ~3 RFCs on package structures.

Compiler time type checking in Nim

I am not an expert in concepts, but I would assume as it's experimental feature a lot of things don't work. As for docs the RFC you linked might be the only place they're documented right now. But there's also an older variant that's has received more [work](https://nim-lang.github.io/Nim/manua

Questions on the current stage of concepts

(I'm deleting an old topic, because my assumptions were wrong.) Can anyone point me to the latest guidance on using concepts? I believe the documentation in the manual is out of date. The best guidance I've found is in this RFC: However, I've having

Problem with a highly recursive function

release is needed otherwise GCC/Clang don't enable tail-call optimization (TCO). Your alternatives is either to rewrite the function to be non-recursive, or use a trampoline or find the GCC/Clang flag that triggers TCO.

Why is the implicit `result` so widely used?

You can use procs and templates to avoid excessive nesting and then you can still see the join points in the control flow graph, whereas you lose them with `return`. But hey, what do I know about formal reasoning...

Compiler time type checking in Nim

It looks like my understanding was pretty far off. For example, the code below works and is checked at compile time. Maybe my issue is with finding the right documentation on concepts. To write the example below, I had to use the RFC: Thanks for th

Problem with a highly recursive function

Surely there is a way. Use the Y combinator. :P

Problem with a highly recursive function

ack(3,14) runs ok if d:release is used. So the question should be modified to ask if there is a way to run the function without d:release or d:danger

Why is the implicit `result` so widely used?

Deep nesting is just as bad as linear programming for the following reasons: 1. When you start with deep nesting, it leads to confusion because: a. You quickly lose track of your main point, which results in problems such as: i. The main point being buried under l

Compiler time type checking in Nim

> but you will get a runtime exception if you pass the function a value whose > type can't be added. ...but type checking a value for being consistent with a > concept is done entirely at runtime. No, neither of these things are true, nim is a compiled language, thus generic type mismatch error

Highly recursive function problem

this is a test

Compiler time type checking in Nim

Hi folks, I was thinking about getting back into Nim, and I was hoping someone could clarify the state of type checking in Nim for me. My understanding is that Nim does less compile time type checking than many other statically typed languages. Notably: 1. When you define a generic function w

Nimble incorrect package structure warning: What is going to be?

It has been reported [numerous](https://github.com/planetis-m/naylib/issues/123) [times](https://github.com/planetis-m/naylib/issues/80) [already](https://github.com/planetis-m/naylib/issues/112) in my library. New users of nim are often confused and scared by this warning. It creates anxiety,

Problem with a highly recursive function

The Ackermann function is non primitive recursive (See the wikipedia article). Is there any way to run ack(3,14) without using d:danger. Using -d:nimCallDepthLimit does not work since the value must be a 16 bit int. proc ack(m,n:int) : int = if m == 0 : return n+1

Claude 3.5 (Sonnet)

It was my own fault for not even considering it might have been as simple as a typo because I had been running it by GPT 4o, which may or may not speak to something about the false sense of security a developer can get when working with LLMs. Going forward I will have a better sense to go about

Claude 3.5 (Sonnet)

Sometimes (when the load is high?) ChatGPT 4o gets dumb.

Why is the implicit `result` so widely used?

The decision tree is there whether you use indentation to outline it or not. If you don't like indentation, fine, but then assembler becomes very attractive.

Releasing Constantine v0.1.0 - A modular cryptography stack for blockchain and proof systems

For those interested in Nim performance vs C, Rust, Go implementations of the same algo, I have made a comprehensive post at

Why is the implicit `result` so widely used?

Seems to be pretty invalid reasoning. This want to be an imperative language. In imperative languages the _main_ structural element of the code is the _order_ of the instructions. Branches are secondary structural elements. If we have early exit, we are using the primary structural tool to do ch

https://www.facebook.com/SmartHempGummiesDischem/

Buy Now Official website:- MAIN BLOGS :-

Nim 2.0.6: invalid type: 'typedesc[seq[EventFuncBool]]' for const

This code compiles without errors in Nim 2.0.6: type MyObj* = ref object of RootObj type EventFuncBool* = proc (myObj: MyObj): bool type MyObjFilter* = ref object of RootObj myObjHandlerBoolSeq: seq[EventFuncBool] # ^ Use ':' instea

Nim 2.0.6: invalid type: 'typedesc[seq[EventFuncBool]]' for const

This code compiles with nim 2.0.4 type MyObj* = ref object of RootObj type MyObjHandler* = proc (myObj: MyObj): bool type MyObjFilter* = ref object of RootObj myObjHandlerBoolSeq = seq[MyObjHandler] Run but nim 2.0.6 gives me the error `inv

is there any progress in NIF? And what is this?

NIF now has a spec:

Smart Hemp Gummies Australia (AU) Official 2024 : Certified

Smart Hemp Gummies Australia (AU) Official 2024 : Certified Australia has seen a rise in the popularity of smart hemp gummies due to their convenient form and possible health advantages. This post will explain what smart hemp gummies are, how they function, what advantages they have, and any pos

Claude 3.5 (Sonnet)

To be fair any human would also pick that up, but most people aren't as easily convinced as LLMs to give up their free time to solve problems for strangers. If you had boiled your code down to a minimal reproduction (and not caught it yourself in the process) you'd have gotten much quicker repli

Nexalyn: 남성 강화 성력 증가 & 파워! 가격?

넥살린 리뷰:- 낮은 성욕과 발기부전은 남성에게 나쁜 영향을 미치기 때문에 인생에서 가장 짜증나는 일입니다. Nexalyn 그들은 또한 체력과 에너지의 저하에 직면했습니다. 이러한 문제로 인해 침대에서 만족스러운 성행위를 할 수 없게 됩니다. 그것은 자연스러운 과정이기 때문에 반드시 일어나야 합니다. 남성 신체의 테스토스테론 호르몬이 특정 연령 이후 감소하기 시작했기 때문입니다. 남성이 30세가 되면 테스토스테론 수치가 젊은 나이만큼 정점에 도달하지 않는다는 사실이 대부분 알려져 문제가 제기된다. 당신의 삶을 원하는 방향으

https://www.facebook.com/Fit.Smart.Fat.Burner.Dragons.Den/

nourishment expended into vitality components. It is prescribed for weight upkeep and moved forward wellness. In expansion to its part in fortifying digestion system, vitamin B3 is advantageous for the skin and apprehensive system.