this post was submitted on 07 Jun 2024
35 points (88.9% liked)
Programming
17408 readers
74 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
formatting does depend on the type of variables. Go look at ktfmt's codebase and come back after you've done so...
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.
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).
I skimmed it. It appears to visit the AST of the code and format that, as any formatter does. ASTs have not been type checked.
Can you give an example?
Precisely! It doesn't know the answer so it has to guess, or make you guess.
You mean how often does the same field name come up more than once? All the time obviously! Think about common names like
id
,size
,begin
,children
, etc. etc.I'm sorry but you clearly haven't thought this through, or you're just happy to ignore the limitations of Ruby. I suspect the latter. Please don't pretend they aren't limitations though. It's ok to say "yes this isn't very good but I like Ruby anyway".