adamant / adamant.tools.editors.vscode Goto Github PK

Something is making it split that operator in code. Figure out what it is and turn it off.

Currently, if you start typing a keyword that isn't used in the current file, it may try to correct it to a different word because it doesn't know that keyword is something you are likely to type. It should always know the keywords of the language are things you might be typing.

The Unicode codepoint escape sequences aren't correctly colorized.

• \uXXXX
• \u(X+)

1. Backticks should not autoclose in code, only in comments
2. Support fenced code blocks set off with three backticks

The special char literals aren't correctly colored.

• '''
• '\'

The underscore will be used to indicate that a value should be inferred or left open. It should be colorized to stand out. Perhaps as a language variable like self.

A document comment block should be treated like a mini markdown document. Paragraphs should automatically be word wrapped.

With the new all-caps naming convention, they will be easy to pick out.

Adamant specifies a specific order for modifiers on functions. The editor should automatically reorder them for you if they are in the wrong order.

Markdown in comments should be styled like a markdown document. For example, "*something*" should be in italics and headers should be styled as such.

Both fenced and inline blocks.

When typing in a doc comment, pressing enter should create a new line that is a doc comment at the same indent depth.

For example:

     /// This is a doc comment↵

Would become:

    /// This is a doc comment  
    /// ‸

Note the space between /// and the caret.

As suggested by Kent Beck in Test-Driven Development: By Example p,105, every time all the tests run and pass make a "checkpoint." That is to say something like a savepoint that can be returned to. Not sure how this relates to source control. Probably shouldn't be a commit.

Variables that are intentionally unused will have names starting with an underscore like in Rust. These names should be given a different color. Perhaps something that blends into the background more.

Some compiler errors have a natural fix. For example, semicolon missing is fixed by putting the semicolon in. For such errors, have a fix button in the error that does it.

In VSCode, typing a close parenthesis (or any other close of an auto-closing pair) when the cursor is to the left of that character always causes it to move the cursor to the right of the character without inserting a character. Instead, it should understand balancing and insert a parenthesis if there are more left parentheses than right. See examples below.

\\ The cursor is represented by '‸'
symbols.Add(new Symbol("fixed"+i+"."+(bitLength-i‸)); // Starting here, press ')'
symbols.Add(new Symbol("fixed"+i+"."+(bitLength-i)‸); // Results in this
symbols.Add(new Symbol("fixed"+i+"."+(bitLength-i)‸)); // Should result in this (VS does this)

symbols.Add(new Symbol("fixed"+i+"."+(bitLength-i‸))); // Starting here, press ')'
symbols.Add(new Symbol("fixed"+i+"."+(bitLength-i)‸)); // Currently and should continue to result in this