Bunch of ocaml features

[QuentinRa]

SPLIT THIS ISSUE

• if a variable is not stored -> suggest store
• if true then true else true

Before

if something then true else false

After

something

• Generate line to print something
• missing try-catch
• boolean is always inverted
• usage of == instead of = ? usage of != ?
• usage of "!true" instead of "not true"
• copy of " in a string -> escape
  (done? injection)
• try-catch branchs
• matches

Before

type t = A

let x y = match y with
| 0 -> A
| 1 -> A
| 2 -> A

After

type t = A

let x y = match y with
| 0 | 1 | 2 -> A

or

Before

type t = A | B | C

let x y = match y with
| A -> 0
| _ -> 1
| C -> 2

After v1

type t = A | B | C

let x y = match y with
| A -> 0
| C -> 2
| _ -> 1

After v2

type t = A | B | C

let x y = match y with
| A -> 0
| _ -> 1

• indents
• imports/open?
• in Java, every return is shown when clicking on one

[QuentinRa]

Another bunch of notes

Scope

• go to the declaration of a variable
• go to the declaration of a function
• go to the declaration of a constructor
• go to the declaration of a type
• find the usages of a variable
• find the usages of a function
• find the usages of a constructor
• find the usages of a type
• Go back is working with native functions/Modules

Autocompletion

• Show suggestions from the library
• Show the type of the suggestion
• Take the context into account

Smart coding

• Copy ml - mli
  • Show a whole module in yellow if there is a missing property from a module pasted in the .ml
  • Show the warning in the .mli too, with a quick fix
  • The pasted code in the ml should be compacted (as IntelliJ does with the documentation in others languages)
  • Action to generate a .ml from a .mli?
  • Warning if the order of the items in the .ml is different from the one in the .mli
• Variables
  • if a variable is hiding (already one in the scope) another, show a warning
    • let [...] var
    • match ... with | C(vars)
  • Show the type of every or most variables
• Syntax
  • Error is there are an "in" right-after another one (-> the programmer added an in and a new line then another in, or the programmer removed a line, etc.)
• Partial functions should be highlighted in a way that the programmer should notice that we got missing arguments (if that was not intended)
• Action: "value" to let _ = value
• Action: "value" to let _ = Format.printf value
• Warning if missing try-catch
• Imports on the fly
• Show warning if wrong indent