Abandoned it? What?
Abandoned it? What?
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.
Dispersed camping. We plan the day before we decide to go. A lot fewer people, dogs can be off leash, etc.
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.
Nighthawk in light shows how to make your own on YouTube. He has lots of videos about stuff like this. Someone else in the comments linked one of his vids.
So different thickness materials can actually cool you off just from a heat transfer perspective, completely ignoring the PCM capabilities (I didn’t click your link I’m just assuming it’s his latest vid). https://www.thermal-engineering.org/what-is-critical-thickness-of-insulation-critical-radius-definition/
So wearing a thin tshirt in cold weather for example can actually be colder than wearing no shirt at all. Same in reverse. I’m wondering if this material is doing that rather than being some sort of PCM.
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.
I’m still looking for the glasses to show op is a professional.
They said they know about that, but it’s ridiculous.
The other is a misprint appearing in Deuteronomy 5: the word “greatness” appearing as “great-asse”, leading to a sentence reading: “Behold, the LORD our God hath shewed us his glory and his great-asse”.
Hehehe
Ligatures make code way easier to read, especially if you’re using lambdas or a language with different comparison operators than “normal”.
It says 2023, not 24. Commenter typo’d. and the top number is correct. Bottom one is probably custom filled out, not based on actual work history.
There’s not even an e after the l
Just use asdf or the alternative that works on windows. You can specify all your languages in the file even for maven or gradle or any thing else as well. No more managing installs.
Maybe other Ruby code is better, but people always say Rails is the killer app of Ruby so…
I’ve literally never heard anyone say that…
That only works if you have static type annotations, which seems to be very rare in the Ruby world.
no. it literally works for any ruby code in any project. you do not need static type annotations at all. I can tell you’ve literally never even tried this…
Well, I agree you shouldn’t use Ruby for large projects like Gitlab. But why use it for anything?
because it’s a fantastic scripting language with a runtime that is available on almost every platform on the planet by default (yes most linux distributions include it, compared to something like python which is hardly ever included and if it is it’s 2.x instead of 3.x). It’s also much more readable than bash, python, javascript, etc. so writing a readable (and runnable everywhere) script is dead simple. Writing CLIs with it is also dead simple, while I think Python has a few better libraries for this like Click, Ruby is much more portable than Python (this isn’t my opinion, this is experience from shipping both ruby and python clis for years).
What do you mean by illegal? How can a technique be illegal?