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
lgritz opened this issue
Feb 19, 2024
· 0 comments
Labels
core APIsAffecting public APIs of core functionality classes, such as ImageInput, ImageOutput, ImageBuf.roadmapThis is a priority item on the roadmap for the next major release.
This task is to scrub the major APIs and eliminate as many places (as is practical, we know some may be harder than others) where we have API calls that take a pointer and size (or worse -- just a pointer and an assumption about the size), and instead use span<T>/cspan<T> for things that are like arrays, and string_view for things that are like strings.
For calls falling into this category, we'll have to decide on a case-by-case basis whether to (a) add a new variety of the call that takes a span, deprecating the old one, (b) replace the old one entirely.
Just as a way to seed you with ideas, and since this work can be parallelized by different people taking different classes, here is a list of some headers that probably contain functions that could use this cleanup:
argparse.h
deepdata.h
imagebuf.h
imagebufalgo.h
imagecache.h
imageio.h
paramlist.h
strutil.h
texture.h
The text was updated successfully, but these errors were encountered:
lgritz
added
core APIs
Affecting public APIs of core functionality classes, such as ImageInput, ImageOutput, ImageBuf.
roadmap
This is a priority item on the roadmap for the next major release.
labels
Feb 19, 2024
core APIsAffecting public APIs of core functionality classes, such as ImageInput, ImageOutput, ImageBuf.roadmapThis is a priority item on the roadmap for the next major release.
This task is to scrub the major APIs and eliminate as many places (as is practical, we know some may be harder than others) where we have API calls that take a pointer and size (or worse -- just a pointer and an assumption about the size), and instead use
span<T>
/cspan<T>
for things that are like arrays, andstring_view
for things that are like strings.For calls falling into this category, we'll have to decide on a case-by-case basis whether to (a) add a new variety of the call that takes a span, deprecating the old one, (b) replace the old one entirely.
Just as a way to seed you with ideas, and since this work can be parallelized by different people taking different classes, here is a list of some headers that probably contain functions that could use this cleanup:
The text was updated successfully, but these errors were encountered: