tyler

Not sure if that is a serious question, but it’s because formatting doesn’t depend on the type of variables but going to the definition of a field obviously depends on the type that the field is in.

formatting does depend on the type of variables. Go look at ktfmt's codebase and come back after you've done so...

Maybe my example was not clear enough for you - I guess it’s possible you’ve never experienced working intellisense, so you don’t understand the feature I’m describing.

Lol, nice try with the insult there. I code in Kotlin, my intellisense works just fine. I just think you're quite ignorant and have no clue what you're actually talking about.

Ctrl-click on bar. Where does it jump to?

it gives you an option, just like if it was an interface. Did you actually try this out before commenting? Guessing not. And how often are you naming functions the exact same thing across two different classes without using an interface? And if you were using an interface intellisense would work the exact same way, giving you the option to jump to any of the implementations.

I'm sorry, but you clearly haven't thought this out, or you're really quite ignorant as to how intellisense works in all languages (including Ruby, and including statically typed languages).

It’s happening on lemmy too. People making posts in multiple subs saying that FF is super buggy, etc.

Reynolds wrap literally has this as a faq on their website because so many people think it.

By using the AST? Do you really not know how languages work? I mean seriously, this is incredibly basic stuff. You don’t need to know the type to jump to the ast node location. Do you think that formatters for dynamic languages need to know the type in order to format them properly? Then why in the world would you need it to know where to jump to in a type definition!?!

Edit: also in the case of Ruby, the entire thing runs on a VM which used to be YARV but I think might have changed recently. So there’s literally bytecode providing all the information needed to run it. I highly recommend reading a book about how the Ruby internals work since you seem to think you understand but it’s quite clear you don’t, or for some reason think “jump to” is this magical thing that requires types.

Oh 😅

Jump to declarations or usages has absolutely nothing to do with types so I have no clue why you think type annotations to make jump to useful.

Was pretty sure before clicking it was going to be Colorado and lo-and-behold. Colorado is killing it with everything lately.

I’m still looking for the glasses to show op is a professional.

American here. Never heard of it.

Depends on your reference frame

They said they know about that, but it’s ridiculous.

Ligatures make code way easier to read, especially if you’re using lambdas or a language with different comparison operators than “normal”.