Ironically enough I do want people to benchmark Bolin. It's very performant. I didn't want to modify the EULA and accidentally put a hole in it. I'll definitely

Ironically enough I do want people to benchmark Bolin. It's very performant. I didn't want to modify the EULA and accidentally put a hole in it. I'll definitely have a new one when the compiler gets to 1.0 The compiler should complain about aliasing but I should check when I get home. The problem here is array's have an invalidation function (it may resize and the pointer may change). It's not allowed to have aliases. If the compiler knows what type is expected (for the enum/bitflag) it can figure out the value. 2. No, its highly dependent on knowing the type. Yes, first argument. _OnBreak can see the index if you have it but I can't remember if it lets you see v2. It should but I never actually tested it > they pick them because they NEED what the unique features help them accomplish If you read it off a list would you recognize what it does? People in the last 24hrs told me they don't understand why I would want onbreak and didnt notice you can chain breaks so you don't need a goto > That's not a good trade. It's tough. One goal is how to make the developers lives easier. I heard about people quitting their project because of comments over github