Programming

vascorsd, 5 days ago

@dwardoric seeing too deep nesting and the code running off the screen to the right kinda screams at you to try and simplify it earlier and to move things to other functions 🤔

vascorsd, 5 days ago

@ragb it's easy to mix them. For understanding when and how to use them you need a deep understanding of what they are meant to be used for, which newbies won't know or understand earlier in their career.

It happened a lot having parameters that you want to align and variable declarations and other things, but then having the tab key not expanding automatically to spaces means that you will use it in the middle of code to try to align things accidentally and inherently things will end up mixed.

omalley, 4 days ago

@oblomov most of the newer languages (eg. #RustLang or #GoLang) don’t support inheritance between classes/structs. They only support implementation of traits, which only define interface and not implementation. In general, using inheritance for implementation reuse is brittle and I like to avoid it.

oblomov, 4 days ago

@omalley as interesting this may be, it's not really what I was asking about 8-D

vascorsd, 6 days ago

This library is better than official scala docs where I spent some hours the other day navigating the confusion of some Collections trying to understand the different ways I could create an ordered Map and basically giving up on the idea because I was unsure of what I should use.

I mean I eventually got the information I wanted, but it was from jumping between google, stack overflow, scala main page and a bunch of api docs.

But it didn't left with with any confidence for what I was doing.

😮‍💨

vascorsd, 6 days ago

In general the official #scala API docs are very very lacking and generally suck.

Methods have barely any description on them. There are no examples in most methods to understand them. Important methods and collections lack explanation of their characteristics related to performance, runtime, O notations of each etc. Barely describe where each is more appropriate vs others, etc.

🫣

BentiGorlich, 4 days ago

@melroy
Maybe that would be a good idea 🤔

Btw I was impressed to learn that federation for messages is not only not working it is not implemented at all 😅

melroy, 4 days ago

@BentiGorlich It is indeed not implemented at all in kbin indeed. It never was. So if we implement this, then Mbin has another new bullet point for on the readme page ;P

davesmith00000, 5 days ago

@vascorsd This had me stumped for a long time, too! Here is how I think you're supposed to do it:

enum AST:  
 case Str(v: String)  
 case Num(i: Int)

object AST:  
 object Str:  
 extension (s: Str)  
 def foo: String = "value: " + s.v

AST.Str("Hello").foo  
// AST.Num(0).foo // Does not compile  

vascorsd, 5 days ago

@davesmith00000 yeah that works. I ended up also using some of those extensions for the enum members as well for their companion objects. Like

extension (so: Str.type) {  
 def empty = ...  
}  

Kinda works, which is nice.

It's a little frustrating that I can't do

extension (_: Str.type) or extension (Str.type).

Extensions and enums kinda pair well with each other.

taxorubio, 5 days ago

I hereby declare war on int.

numeredevs, 5 days ago

@taxorubio Yeah, especially important, if you write files in binary mode and don't lock the bit sizes. We had that problem also during the 64 bit migration

bcon, 4 days ago

@dominucco not pictured is a mirror. Jar Jar is all about his tricks… sneaky Jar Jar

hankg, 4 days ago

@dominucco …at least they got the fingers right for once, ironically lol…