Library work not allowed anymore

[Martinhinnerson]

Hi!
I work in a project where library 'work' is expected to be used globally for all files. After updating vhdl_ls it does not work anymore since the library 'work' is not allowed in the vhdl_ls.toml anymore.

I tried building vhdl_ls locally and just remove the check in vhdl_lang/src/config.rs that returns an error if work is used, and that seems to work.

What was the reason to disallow this?
If you cant remove it again, would it be possible to have a config option to allow library work again?

[Xcodo]

Work can still be used in VHDL use statements, where it means "the current library". See this blog post for a brief explanation.

You don't need to change your VHDL files to use VHDL-LS, refering to modules as use work. is fine.

However, work is not allowed in the vhdl_ls.toml configuration file as the name of the library. Instead you can use any other name, for instance work_lib would be valid.

[Martinhinnerson]

Thanks for the reply. I’m aware that work is not really a library, but I tried naming it defaultlib in the vhdl_ls.toml and it didn’t work. The language server did not recognize anything imported as work.

How does vhdl_ls know what is the ”current library”?

[Schottkyc137]

How does vhdl_ls know what is the ”current library”?

When you have a vhdl_ls.toml file, you associate a library to each file:

[libraries]
libA.files = [
    "foo.vhd",
    "bar.vhd",
]

libB.files = [
    "baz.vhd",
    "foobar.vhd",
]

When you edit foo.vhd, the work library will be set to libA. So visible symbols from the work library will include symbols from foo.vhd and bar.vhd. Similarly, if you edit stuff in baz.vhd, the work library is libB and therefore symbols from baz.vhd and foobar.vhd