Re: 2.x.x (and earier?): yet another decoding SSHA issue

Would this solve the issue to your satisfaction for 3.0.0 at least, or do see it as more magical unexpected behaviour?

Please no magical behaviour. Can't the cast/reference stuff be used to do this "properly"?