I am thinking about the best way to get continual feedback with more detailed type hints in VSCode. Similar to how it is done with rust-analyzer. Background For those who haven’t used Rust, here’s what the feedback loop looks like when you are coding: I really want to have the same thing in …

Cross posting from Immediate, Rust-level type hints · Issue #3597 · julia-vscode/julia-vscode (github.com) This is along the lines of what I wanted to do initially, but one reason I switched was that there was a desire to not load/ execute user code in the LSP. This seems like a good idea if we ca…

Having something like that would be really cool. The definition of the calls could follow something of the @testitem structure. Something that could be placed clearly alongside the function: foo(x) = x .+ 1 @test_inferred "foo" begin foo([1]) foo(Any[1]) end such that the calls of foo def…

Maybe a macro like @lmiq suggested would be better. However I don’t think it should be parsed by anything other than the LSP, which makes it a bit tricky. (what macro symbol would you use? And would you have to depend on some package to get it?) This is why JuliaFormatter has these comment-based co…

[image] Zentrik: Another concern would be if Cthulhu would be fast enough, iirc the main reasons why it’s slow is pretty printing types and compilation. Presumably if we’re rerunning Cthulhu a lot we could ensure it’s caching things appropriately so that it is able to be fast. @code_warntype …

We have thought about something like this before, but it’s never really gone anywhere due to no-one interested really having time to push this forward. Generally, I really don’t want the normal LS process loading any user or package code. That said, we can create an additional communication channel…

Just to bring up this point: [image] pfitzseb: Generally, I really don’t want the normal LS process loading any user or package code. I can understand the security implications, but what about having it be opt-in? For comparison, rust-analyzer actually does load and execute arbitrary user co…

[image] MilesCranmer: If I have to keep track of some other file that has all the inference statements, I will probably end up just not doing it. the @testitem framework exactly provides the functionality to put the tests just side by side the function, and they appear in the VSCode test suit…

[image] MilesCranmer: I can understand the security implications, but what about having it be opt-in? I’m less worried about security, and more about stability. Though tbf, this might be less of an issue by running the LS-internal functions in a fixed world, so that user code can’t mess with …

[image] pfitzseb: All in all, 1. seems pretty feasible and might be a good-enough experience imo. Obviously this is your call if you’re the implementer but I must say from a user perspective (3) sounds much better. I would prefer to offload all the complexity of IDE state management onto you…

Makes sense to me. And I guess the security wouldn’t even be an issue since there are already many known ways to do code injection in VSCode (hence the “Do you trust the authors…” pop up). i.e., no harm from having it be the default. And like @jar1 I really like option 3. I think you could use OS u…

Towards Rust-level feedback on type stability

Tooling

MilesCranmer May 24, 2024, 6:48pm 18

Hacking on an implementation of @stable in this thread: Improving speed of runtime dispatch detector

Topic		Replies	Views
Does Julia syntax do enough to encourage type stability? Internals & Design type-stability	22	5068	February 22, 2017
Comparison of Julia with statically typed languages New to Julia question	10	2397	June 9, 2024
HN comment on Julia vs Swift type checking and auto diff Machine Learning	24	3054	May 14, 2019
Julia language server, return type declarations, type stability New to Julia question	4	663	December 30, 2021
[ANN] DispatchDoctor.jl :stethoscope: – offers you a prescription for type stability Package Announcements	45	2972	June 4, 2024

Towards Rust-level feedback on type stability

Related topics