11:28:17stassatsand nothing calls it, so, yeah, it's approximately completely broken
14:27:55mrottenkolberI get a lot of "note: doing unsigned word to integer coercion (cost 20)", apparently because my struct slots are (unsigned-byte 64). Any hints of avoiding this (i.e. inlining slot accessors)?
14:28:15mrottenkolber(I get this exclusively due to struct writes I think)
14:39:49|3b|does the compiler know the value you are writing fits in the slot?
14:40:31|3b|if not, giving it more information (and/or making sure yourself) might help
15:10:36fiddlerwoaroofstassats: interesting, is this a bug?
15:52:20Bicyclidinei think that means that the problem is that the function returns one of those typed values, which means they have to be boxed (coerced)