Opened 10 years ago
Closed 4 years ago
#8144 closed Patches (duplicate)
Document locator and cached_location_t
| Reported by: | Mateusz Loskot | Owned by: | chhenning |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | gil USE GITHUB |
| Version: | Boost Development Trunk | Severity: | Not Applicable |
| Keywords: | documentation | Cc: | mateusz@… |
Description
I've stumbled upon old thread on locator and cached_location_t. There are some interesting explanations which I believe is worth to add to Boost.GIL docs.
Particularly, I believe the following Lubomir's clarification should be added as first paragraph documenting cached location:
Cached location is meant to be used as a quick way to get to neighborhood pixels if you need to read or write a neighboring location frequently relative to a given locator.
Currently, notion of cached location is documented in the GIL design guide but it makes users to deduce answer to What the cached locator is for?
Change History (2)
comment:1 by , 6 years ago
| Cc: | added |
|---|
comment:2 by , 4 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Moved to https://github.com/boostorg/gil/issues/130