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
Just wondering why the return type of put is T&? (same for get).
I don't really see why these functions return the value we feed them with.
I wonder if it wouldn't make more sense to have put return the next writable location, kind of like putString.
That way, it would become possible to save structs one after another, by using the returned value as the next address.
Perhaps it would also make sense if get just returned void.
What do you guys think?
Your workbench
Not relevant.
Steps to reproduce
Not relevant.
Expected behavior
Not relevant.
Actual behavior
Not relevant.
The text was updated successfully, but these errors were encountered:
Hi, no worries.
I think it would be a lot nicer if put returned the next writable address.
That'd be quite useful, in fact, as it would allow to chain calls to put quite easily.
Subject of the issue
Just wondering why the return type of
put
isT&
? (same forget
).I don't really see why these functions return the value we feed them with.
I wonder if it wouldn't make more sense to have
put
return the next writable location, kind of likeputString
.That way, it would become possible to save structs one after another, by using the returned value as the next address.
Perhaps it would also make sense if
get
just returned void.What do you guys think?
Your workbench
Steps to reproduce
Not relevant.
Expected behavior
Not relevant.
Actual behavior
Not relevant.
The text was updated successfully, but these errors were encountered: