I've adjusted my implementations for Object.fromEn...

# javascript

[Bernhard]

I've adjusted my implementations for Object.fromEntries: what is the purpose of returning ReadonlyRecord instead of record? technically speaking, there's nothing that would prohibit you from modifying the newly constructed JS object again.

In the Kotlin std lib, the default implementations are immutable, so you get a covariant list by default. So I think we should return a Record instead from fromEntries or provide a fromEntriesMutable version

[turansky]

or add copy method for transformation?

[turansky]

Could you share your use case?

[Bernhard]

sorry, was in a game 🙂

[Bernhard]

let me look up copy

[Bernhard]

ok, does not seem like one is available/generated for records

[Bernhard]

in general I think copying wouldn't be a huge performance hit since you're just copying pointers

[Bernhard]

as for my use case: function/method signature compatibility mostly

[Bernhard]

imagine having methods that work on mutable records and now you want to pass in a non mutable one

[Bernhard]

if it's doable in an easy fashion, you can just adjust the signatures across the board, otherwise you probably want to cast to a mutable one since there's basically no difference

[Bernhard]

now Object.freeze, that would make a difference

[Bernhard]

at least for fromEntries, I think there should be to ways that you can choose from, similar to sequence.toList() vs sequence.toMutableList()

[Bernhard]

and ideally, immutability is ensured by using Object.freeze on the readonly one

[Bernhard]

at least the current situation neither translates to what you'd expect from that JS method (every object is mutable by default) nor are there parallels to how the kotlin stdlib does things

[Bernhard]

either way, I don't have hard feelings about how it'll be implemented eventually but it might make sense to make it behave close to the JS or Kotlin stdlib defaults

[turansky]

imagine having methods that work on mutable records

Please no 🙂

[turansky]

For me it’s like methods, which receive MutableList as parameter - it doesn’t look like Kotlin way

[Bernhard]

I guess the solution then is to go for something similar to copy

[Bernhard]

the JS APIs kinda got me back into JS brain

[Bernhard]

just realized we had anonymous objects as well in Kotlin this evening