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
The recent revision of the proposed MLBuffer spec no longer represents a low-level concept of device memory storage, as these buffers are now tied to specific shapes and data types. Converting between MLBuffer(s) of different sizes will likely require copying (vs reinterpret_cast). To avoid confusion with other 'buffer-as-bytes' types (e.g., GPUBuffer, ArrayBuffer), I propose renaming MLBuffer to MLTensor.
👍 = I vote yes to rename
The text was updated successfully, but these errors were encountered:
MLBuffer never made it into the spec, so the only artifacts saying "MLBuffer" are issues and PRs (and lots of Chromium code which @bbernhar has been diligently refactoring). We could retitle issues including MLBuffer. The explainer PR already uses MLTensor. Otherwise... I think we can close this? :)
The recent revision of the proposed MLBuffer spec no longer represents a low-level concept of device memory storage, as these buffers are now tied to specific shapes and data types. Converting between MLBuffer(s) of different sizes will likely require copying (vs
reinterpret_cast
). To avoid confusion with other 'buffer-as-bytes' types (e.g., GPUBuffer, ArrayBuffer), I propose renamingMLBuffer
toMLTensor
.👍 = I vote yes to rename
The text was updated successfully, but these errors were encountered: