Haled Odat

> @HalidOdat how are you handling boxing, unboxing of primitive values? I think I left set_field and get_field on value so things like `“hello world ”.trim()` would still work We...

> Hey @HalidOdat I found this interesting and am trying to tackle it. > To ensure I'm following your "vision", methods from builtins like `Array` would stop receiving `&Value` as...

> One thing I was wondering, would the `global_obj` in `Realm` become an `Object`/`GcObject` or would it remain a `Value`? > And if it does change, which would be more...

> Hey @HalidOdat any idea on what I should try to change next? I was trying to change `Value::new_object` to return `GcObject`, which should probably also move to `Object`, but...

> @HalidOdat from my work on #854 it would be good to stack-allocate Values, but as some of them hold RCObjects its not possible. There is a problem with objects...

Many refactors/changes have been done since this issue was created and they have been resolved. So closing this :)

> @HalidOdat any news on this? Do you want me to un-assign it from you? Maybe after #1373 I can start working on this, but until then I'll un-assign myself,...

> @HalidOdat I see you assigned yourself this issue, let me know if you're still working on it, or if we can un-assign it :) I didn't implement this because...

> Still, having integer operations optimized would be a good thing, right? Do you see a way we could get this? An option might be to use untagged enums (unions)...

> I was thinking about some possible optimizations, and I think we could optimize `JsString` by only storing `UTF-16` if the string has characters outside of the ASCII range, and...