You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love the idea of doing something like this but I wonder if we've fully identified the value, or agreed on WHY we are doing this. I do a lot of programming bouncing between Perl and Golang which is strongly typed and the thing I miss the most about Go when I'm back in Perl is how useful the type information is for tooling and debugging. Like I can hover over a method and get details about its required signature and its return value, which in Perl often I end up having to add a lot of Data::Dumper statements to figure out what something is doing. This is more valuable with complex, large codebases. But it seems like we are focusing on runtime checking, is that correct? What is the barrier to having type information introspect able via the compiler so that we can support in in a Language::Server?
The text was updated successfully, but these errors were encountered:
I love the idea of doing something like this but I wonder if we've fully identified the value, or agreed on WHY we are doing this. I do a lot of programming bouncing between Perl and Golang which is strongly typed and the thing I miss the most about Go when I'm back in Perl is how useful the type information is for tooling and debugging. Like I can hover over a method and get details about its required signature and its return value, which in Perl often I end up having to add a lot of Data::Dumper statements to figure out what something is doing. This is more valuable with complex, large codebases. But it seems like we are focusing on runtime checking, is that correct? What is the barrier to having type information introspect able via the compiler so that we can support in in a Language::Server?
The text was updated successfully, but these errors were encountered: