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
Currently users have to use the count property of a LaserFrame to determine how many slots are active. It might be good syntactic sugar for lf.property to actually return lf.property[0:lf.count] so the user doesn't have to do that each time.
Might require "property" to be allocated internally as "_property" to get access to the full array while lf.property returns the view.
Currently users have to use the
count
property of a LaserFrame to determine how many slots are active. It might be good syntactic sugar for lf.property to actually return lf.property[0:lf.count] so the user doesn't have to do that each time.Might require "property" to be allocated internally as "_property" to get access to the full array while lf.property returns the view.
I.e.,
lf.add_scalar_property("property")
->setattr(self, "_" + name, np.full(self._capacity, default, dtype=dtype))
lf.property
->lf._property[0:lf.count]
The text was updated successfully, but these errors were encountered: