You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made an API proposal for the .NET BCL yesterday and in retrospect I was probably a bit naive in my approach.
Still, I'd be happy for some feedback on it..
If it's just a terrible idea in general, I'd also accept that 😅
TLDR; I'd like the standard library to have some semantic understanding of wrappers; short example :
publicclassMyWrapper<T>{publicTValue{get;set;}}
In the case of Mapster, my thought is that the library would automatically understand that what it should do with that type is copy the wrapped value, and not the enclosing object. In other words, instead of Id = 42 it should recognize it as just 42, without individual programmers needing to implement this logic manually
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I made an API proposal for the .NET BCL yesterday and in retrospect I was probably a bit naive in my approach.
Still, I'd be happy for some feedback on it..
If it's just a terrible idea in general, I'd also accept that 😅
dotnet/runtime#101023
TLDR; I'd like the standard library to have some semantic understanding of wrappers; short example :
In the case of Mapster, my thought is that the library would automatically understand that what it should do with that type is copy the wrapped value, and not the enclosing object. In other words, instead of
Id = 42
it should recognize it as just42
, without individual programmers needing to implement this logic manuallyBeta Was this translation helpful? Give feedback.
All reactions