ZacNugent

Allow using statements to point to live package code

10

Partner of https://github.com/julia-vscode/StaticLint.jl/pull/103 The key question at this point is what files we will allow/determine to be packages. One approach would be to limit it to workspace folders that have...

We need to actually check the client's capabilities on startup and adjust the responses to requests accordingly, for example not all clients support snippet completions.

Partner piece to https://github.com/julia-vscode/StaticLint.jl/pull/134

WIP - add parsing/scoping capabilities for edits to single tokens

3

An attempt to limit the amount of work done for static analysis. This identifies edits that can be made by altering terminal expr (i.e. those without child expr, such as...

Create fake env when using a package dir as an env

6

I've not tried this but feel it should work. When the target env dir is a package it modifies the Project.toml, adding the parent package + packages in `extras`.

Add some inference based on use of getfield.

6

This adds another inference pass to non-toplevel scopes. Type information is added for bindings where `getfield` is used on the variable through the dot operator. ```julia struct T somefieldname1 end...

```julia using Tokenize collect(tokenize("0x.")) ```