No. Greek Semicolons hold no power here.

Replacing semicolons with Greek question marks? Easy fix.

Terminating identifiers with Greek question marks? Pure evil.

5

May work. May not. Haven't tested.

You know what does work as a variable name? ಠ_ಠ

1

Imagine not programming in Vim 💀

2

nvim + coc.nvim + coc-clangd (or other language LSP implementations) will give you the conveniences of modern IDEs + the power and speed of vim 🙂

1
- Vim again, showing why the superior text editor.
  
  1
Just throwing in Helix here.

0
- I use Helix and Nvim pretty much concurrently and whenever I have to use vim I feel slower on most basic movements. A fresh set of keybinds is really nice - though simultaneously there are one or two specific actions which are slower or unintuitive in Helix. But overall I love Helix.
  
  1

error: unknown start of token: \u{37e}
 --> src/main.rs:2:30
  |
2 |     println!("Hello, world!");
  |                              ^
  |
help: Unicode character ';' (Greek Question Mark) looks like ';' (Semicolon), but it is not
  |
2 |     println!("Hello, world!");
  |                              ~

error: could not compile `playground` (bin "playground") due to previous error

2

That’s a well designed compiler.

2
- I would rather see it just added to the standard definition as a valid character, so the compilation passes without issues. It would make lives of Greek programmers a little bit easier!
  
  But on a second though, it would probably make the lives of compiler programmers a living hell. Having to deal with two symbols for one thing sounds really annoying :D
  
  1

I love that this implies Visual Studio is not worth its salt, because it most certainly isn't.

1

Depends on the language.

For .net, it's pretty hard to beat.

For anything else, I use vscode. Its a great all-around IDE/editor.

2
- I prefer Rider over VS but I like VS Code too
  
  2
Visual Studio is pretty good.

0
- You should check out Jetbrains Rider. It feels like cheating. Or ReSharper if you can't leave VS completely
  
  1

This would bite me in the ass because I often ignore these kinds of warnings in VSCode (SFDX for VSC is kinda crap, warns you about nonissues, and often doesn't correctly identify the problem).

0

Maybe have a look into Gremlins Tracker

1
Confusable characters get a little yellow box which is different from the squiggly underlines most linters and stuff use which at least makes it a bit more recogniseable.

Personally I can't stand having underlines all over my code, so I'll usually just "fix" the non-issue if possible, or otherwise just disable whatever the warning is entirely.

0
- Ahh the solution is simple, in VS Code add these lines to your general config
  
  "workbench.colorCustomizations": { "editorError.foreground": "#00000000", "editorWarning.foreground": "#00000000", "editorInfo.foreground": "#00000000", },
  
  Then get the error lens extension, it's so much more pleasant. Visual example
  
  1