Re: [Capy review] Some questions
Steve Gerbino via Boost <[email protected]> Tue, 23 Jun 2026 18:15:06 +0000
| Newsgroups | gmane.comp.lib.boost.devel |
|---|---|
| Message-ID | <8Zof0b8YORnQLS7SrMRr3i6fF7zy_uTFmx5UJ2GvC4r1do6wUhIOxEFcESTYbGGdG-f9SmheTBBQo04EoCuMT1onKQSMau9kBtIDXEa5ue8=@gerbino.co> |
On Tuesday, June 23rd, 2026 at 8:08 PM, Ruben Perez via Boost <[email protected]> wrote: > > > > > 4) Does capy::cond::canceled add anything vs. just using > > > > > std::errc::operation_canceled? > > > > > > > > No, it doesn't. It is there for consistency with our error types that > > don't have std spellings. > > > > > > Would it make sense to just use the errc one and remove capy's? Maybe > > > Peter can suggest something here? > > > > We have a convention throughout the project to always compare against > > error conditions. Making a change like that would make it the oddball. > > > Why? std::errc is an error condition enum, not an error code enum. To clarify, I mean our error conditions as indicated here: https://develop.capy.cpp.al/capy/reference/boost/capy/cond.html "These are the conditions callers should compare against when handling errors from capy operations." _______________________________________________ Boost mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/[email protected]/message/6HTBH5RSFN5XLI53DFWGCJQ2PK34MSE2/