In general, JETLS helps a lot. But some warnings I would like to suppress, for example this one:
`ADD_MIRROR` is not concretized but JET needs to use its actual value in order to define types or methods.
- If this binding can be declared as a constant, try to declare it as a constant (i.e. `const ADD_MIRROR = ...`).
- You may need to specify `:(ADD_MIRROR = x_)` pattern to the `concretization_patterns`
configuration to allow JET to actually evaluate this binding, e.g.,
`report_file("path/to/file.jl"; concretization_patterns = [:(ADD_MIRROR = x_)])`.
- If the above approaches do not work, try `concretization_patterns = [:(x_)]` to
concretize all top-level code in the module (recommended as a last resort since it
would incur any side effects in your code and may cause the analysis to take longer time).
I already have the following lines in my .JETLSConfig.toml file, but it does not help:
[[diagnostic.patterns]]
pattern = "not concretized"
match_by = "message"
match_type = "regex"
severity = "off"
Any idea?