Multiline conditions

also if you need multi line maybe its best to assign it? let alive = a.blablabla == b.blablabla or a.blobloblo == b.blobloblo active = c.blablabla == d.blablabla or c.blobloblo == d.blobloblo if alive and active: doo stuff Run

Nim - plugin for IntelliJ IDEs | JetBrains

TabNine can provide suggestions based on a lot of open-source projects which they analysed, and also based on the patterns in your project(s). It's not limited to normal variable suggestions, it can autocomplete whole lines

Nim - plugin for IntelliJ IDEs | JetBrains

How does Tabnine work ? Installing it alongside Nim's VS Code extension would add it's functionality along side the extension ?

Multiline conditions

Gracias.

Help me to configure (neo)vim, please

I followed to set up nimlsp and i like it much better than syntastic

Notification about new replies and @{name} etc

Thanks very much for your confirmation! (and I am sorry for a very late reply... I will rearrange my URL bookmarks more neatly :)

Nim - plugin for IntelliJ IDEs | JetBrains

First: Thanks. Second: Yuck, yet another bloated fat monstrosity. I'd love to see a comparably fully featured as VSC plugin for Sublime Text (which seems to be the most widely used serious but small dev. editor other than Vim).

Multiline conditions

Hello world. In Javascript, Im used to write long and complex conditions on several lines, with many parentheses, just like this: if ( (a.blablabla == b.blablabla or a.blobloblo == b.blobloblo) || (c.blablabla == d.blablabla or c.blobloblo == d.bl

Multiline conditions

You can do multiline, although you have to put the conjunction ("and", "or") at the end of the line. if a == "A" and b == "B": echo "Huzzah!" Run

What is the problem with the optional end keyword?

Why not write #end comments and make a tool to verify them, if you really want the redundancy?

Help me to configure (neo)vim, please

Hello, I try to configure neovim for having a decent support of nim in it. I've installed **alaviss plugin** and as suggested in the plugin's documentation: **asyncomplete**. I've also installed **syntastic**. **asyncomplete** completes nothing. **alaviss/nim** colorizes and indents ok, search

Nim - plugin for IntelliJ IDEs | JetBrains

I use VSCode because Araq uses VSCode

Nim - plugin for IntelliJ IDEs | JetBrains

the Nim installation for VS-CODE is no longer offered the only alternative is to go to download and load in vs-code

Nim - plugin for IntelliJ IDEs | JetBrains

> Nim is quite in complex as in to know all procedures and types which are > generated via macros you basically have to implement an interpreter and the > majority of the language rules. You can play tricks though and apply heuristics. In fact, I rely quite a bit on "Tabnine" these days and its

Nim - plugin for IntelliJ IDEs | JetBrains

I have some doubts how far this can go. Nim is quite in complex as in to know all procedures and types which are generated via macros you basically have to implement an interpreter and the majority of the language rules. Nimsuggest and all the editor plugins which rely on it come around this by

Nim - plugin for IntelliJ IDEs | JetBrains

IntelliJ is my daily driver, but I mostly stuck to VSCode for Nim because of better support although I otherwise loathe it. Nimatron was a good effort and progress was coming along nicely, but the developer retired it when Jetbrains released their plugin. Still, big props to the developer for hi

What is the problem with the optional end keyword?

> We would use such end keywords only in rare cases, maybe when a proc or loop > is very long or for cryptic critical code. I think there will still be a large number of people adding "end". And there will be disagreements because some people like to put "end" and others hate it.

What is the problem with the optional end keyword?

`moe` is written in Nim. :-) { It could have been called Nim's Own Editor, but "noe" sounds pretty negative. lol ;-) } Anyway, code has always been 2 dimensional for humans even if algos to analyze it are 1-D character/token streams. The significant whitespace debate has always been a "how much

What is the problem with the optional end keyword?

:)

What is the problem with the optional end keyword?

There is also the vertical line drop-down approach as in:

What is the problem with the optional end keyword?

You can use parenthesis for that. If we really want to avoid mistake we would need `end if` `end for` `end proc`. Also I suggest using the indent-rainbow extension (which happen to feature Nim prominently in the demo ;

Looking for collaborators!

Another option is `language-development`, since not all languages are interpreted, not all of them have VMs etc. There is already several different languages implementations (in addition to other lings in this tread) * *

-d:danger versus -d:release --checks:off

> Lots of projects ask the user to use both of them, there is a lot of > misconceptions That was due to a bug in Nim before 1.0. I hope for beginners my explanation is good enough?

What is the problem with the optional end keyword?

I guess it would make some people happy, and I would use it myself if rare cases. The compiler can find the end of blocks by indent, so why not just allow an optional end keyword whenever a block end is detected by the compiler by indent reduction. So allow code like proc startsWi

Nim - plugin for IntelliJ IDEs | JetBrains

> Provides Nim language support. > > *Syntax highlighting - token-based and semantic > > *Syntax errors highlighting > > *Code completion, find usages and refactoring of local unqualified symbols > > *Code folding > > *Structure view > > *Diff

Massive Funding Coming To Nim

How 'massive' are we talking?

-d:danger versus -d:release --checks:off

> But yeah, danger is release + checks:off. And the default config should > probably be simplified to use --checks:off. Lots of projects ask the user to use both of them, there is a lot of misconceptions out there, for example

What is the problem with the optional end keyword?

>so why not just allow an optional end keyword whenever a block end is detected >by the compiler Because I guess it would make some people unhappy to read ugly >(subjetive) code.

Reference to tuple type

You cannot store a type that has a `ref` into a `const`, but you can use them inside compile-time procs in intermediate steps.

Reference to tuple type

I think that paragraph is a bit confusing, ref objects work at compile-time, ptr object do not.

Pointer Arithmetic and constructs like cast[var int](p) += sizeof(a[0])

is his account :)

Pointer Arithmetic and constructs like cast[var int](p) += sizeof(a[0])

> Sad that he left Nim. What happened? Oddly, I cannot search for his posts here, as if the search engine ignores his name. I used to read every post he made.