Github user cramja commented on the issue:
    @jianqiao Sure, that sounds good. @navsan and I talked about another 
alternative which is to call the BitVector constructor instead of `setMemory`. 
I made the `set` method because I thought that it would be cheaper than 
instantiation of an object, but navneet explained that since the compiler would 
pre allocate space on the stack, that the costs would be equivalent. Do you 
think that would be a good alternative?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to