You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For consistency, it would be good to have guidelines on when to use Borrow in contributed code. It would be great if Borrow/Return could be the default for allocation (including new types going forward)- it would make contributing to the code easier, as well as make it easier to manage performance. You could probably do this without too much of a performance hit, although the Borrow/Return functions would need to become a bit more complex to make sure that returns only correspond to borrowed objects. Thoughts on this?
From @kabaka0 on March 22, 2017 14:50
For consistency, it would be good to have guidelines on when to use Borrow in contributed code. It would be great if Borrow/Return could be the default for allocation (including new types going forward)- it would make contributing to the code easier, as well as make it easier to manage performance. You could probably do this without too much of a performance hit, although the Borrow/Return functions would need to become a bit more complex to make sure that returns only correspond to borrowed objects. Thoughts on this?
Copied from original issue: gorgonia/gorgonia#100
The text was updated successfully, but these errors were encountered: