> Well, it looks like having declared a non-static opCall makes the > automatically generated constructor for the struct unusable - which may > or may not be a bug I do think it's a bug. Only a static opCall should interfere with the constructor.