3:46:02fiddlerwoaroofHi, I've been experimenting with generic functions, trying to figure out how things work under the hood
3:46:51fiddlerwoaroofI'm getting a memory fault from trying to call the method-function of a slot accessor in a way that works with normal generic functions
3:47:13fiddlerwoaroofAny ideas about why this is happening? I suspect there is some kind of optimization going on that I'm unaware of.
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