Re: Capy Review

Christian Mazakas via Boost <[email protected]> Fri, 26 Jun 2026 12:07:39 -0700
Newsgroups gmane.comp.lib.boost.devel
Message-ID <CAHf7xWt82r6SmbjUaCx8qa3LFPGWH_ES_sRRR-rnfSGvVZAFUw@mail.gmail.com>
On Fri, Jun 26, 2026 at 11:10 AM Vinnie Falco <[email protected]>
wrote:

> On Fri, Jun 26, 2026 at 10:31 AM Christian Mazakas via Boost <
> [email protected]> wrote:
>
>> ...Capy shouldn't be public.
>>
>
> eh...CERN seems to like Capy
>
> https://github.com/cern-nextgen/wp1.7-traccc/pull/18
>
> They don't use Corosio.
>

First off, congrats.

Second, this confuses me because before you were just saying that it was
unfair to review Capy without reviewing Corosio and that they should be
thought of as "one logical library". That doesn't seem to be the case at
all.

So basically, we _are_ reviewing _two_ separate Boost libraries here. In
principle, I think this is fine but it's just confusing to muddy those
waters. Rainer's review stands then, and isn't a scope error. He has no
onus to look at Corosio.

- Christian
_______________________________________________
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/WCV7GU7MKVWRQMJRTE4BOSL6OT3EAXNH/