Thanks-


On 6/03/2025 7:35 pm, andrew drakeford via SG14 wrote:
> Hi,
> One more concurring opinion: My expectation would be for capacity to
> remain unchanged.
>
> Kind regards
> Andrew Drakeford
>
>
>
>
> ------------------------------------------------------------------------
> *From:* SG14 <sg14-bounces_at_[hidden]> on behalf of Matt Bentley
> via SG14 <sg14_at_[hidden]>
> *Sent:* Wednesday, March 5, 2025 10:58 PM
> *To:* Andre Kostur <andre_at_[hidden]>; sg14_at_[hidden]
> <sg14_at_[hidden]>
> *Cc:* Matt Bentley <mattreecebentley_at_[hidden]>
> *Subject:* Re: [isocpp-sg14] Hive implementation question - would you
> expect assign to decrease capacity() if num < size()?
> Thanks for that-
>
> On 6/03/2025 11:31 am, Andre Kostur wrote:
> > I would suggest that not modifying capacity is the better default.
> > Even clear() doesn't deallocate element blocks.
> >
> > As for insert(num, element) when size() == 0, I would be surprised
> > that if the operation that caused the size to go to zero didn't change
> > the capacity, that the next time I added even 1 element to the
> > container would cause the capacity to drop.
> >
> > For list, I expect the capacity to decrease because list doesn't have
> > a capacity different than size.
> >
> > On Wed, Mar 5, 2025 at 2:06 PM Matt Bentley via SG14
> > <sg14_at_[hidden]> wrote:
> >> Hi all,
> >>
> >> I'm just wondering what people's assumptions are around
> hive::assign()/fill-insert/range-insert and capacity. This is not a
> standardisation question.
> >>
> >> The standard ([sequence.reqmts]) does not specify one way or
> another whether capacity changes as a result of a call to assign(),
> but obviously if the assigned range is larger than capacity(),
> capacity() will increase.
> >>
> >> However, if the assigned range is smaller than capacity, would
> capacity be expected to decrease? Or rather, what would you expect to
> happen? Leave capacity as-is, avoid deallocations and put the burden
> on the developer to call trim()? This has implications for whether or
> not assign does the right thing by cache locality ie. maintaining the
> minimum number of larger contiguous blocks, or by allocation/deallocation.
> >>
> >> For vector, we would possibly expect capacity to stay the same in
> this case. For list, we expect it to decrease.
> >>
> >> Similarly, would you expect a call to hive::insert(num, element)
> when size() == 0 but capacity() > num to potentially decrease capacity()?
> >>
> >> Thanks,
> >>
> >> Matt
> >>
> >> _______________________________________________
> >> SG14 mailing list
> >> SG14_at_[hidden]
> >>
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fsg14&data=05%7C02%7C%7Ccc508ce6b17845129e7a08dd5c39493f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638768123295595493%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1taNyg2HJkMmTK0%2Bp7pkdJHaLHZ9gwhi65Rq9gkRfvM%3D&reserved=0
> <https://lists.isocpp.org/mailman/listinfo.cgi/sg14>
> _______________________________________________
> SG14 mailing list
> SG14_at_[hidden]
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fsg14&data=05%7C02%7C%7Ccc508ce6b17845129e7a08dd5c39493f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638768123295624618%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=bWSvT02pE9UX4D5aarOOIyh3QWhVhSMX8iAVWJrAeJ4%3D&reserved=0
> <https://lists.isocpp.org/mailman/listinfo.cgi/sg14>
>
> _______________________________________________
> SG14 mailing list
> SG14_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg14