Lili Zoey

`Array` will have the hint string be whatever the `TypeStringHint` of `T` is, so you should implement the `TypeStringHint` for your type to have the `2/2:` prefix. `a/b:c` means, "values...

> Wouldn't that be the wrong type string if I use `T` without an array? type strings are specific to when a type is contained in some other type that...

> So I figured out a way to get my enum work both as > > ```rust > #[export] > foo: Foo, > ``` > > and > > ```rust...

I can see a couple of solutions to this: 1. Label the `I*` trait that these methods are in as unsafe 2. Create a separate trait called something like `UnsafeI*`...

> > However when someone implements this trait, they must ensure that the pointer they return from the method satisfies certain criteria. Otherwise they may cause UB. This means that...

> > it's also not the case that constructing the `Checked` can actually ever lead to any UB, the UB happens when the `Checked` is returned. and that's something we...

ok so that does mean that option 3 is likely entirely viable which makes the discussion partially moot. we could still have option 2 as a fallback in cases where...

unfortunately we cannot rely on a user-generated count method always returning the right length of such a slice, since there's nothing stopping a user from just returning different lengths every...

the user is still free to return differently sized slices from `shaped_text_get_glyphs` for the same `Rid`, which could cause UB in this case.

if we're gonna fix this to be correct we should actually make it correct. if we can't find some good relatively simple way to do this correctly then we should...