On August 20, 2020 7:08:06 PM EDT, David Feuer wrote:
>So I guess this is to avoid having to check the closure type on each
>mutation to see if the array needs to be added to the mutable list?
>
Correct.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
So I guess this is to avoid having to check the closure type on each
mutation to see if the array needs to be added to the mutable list?
On Thu, Aug 20, 2020, 6:12 PM Bertram Felgenhauer via Glasgow-haskell-users
wrote:
> David Feuer wrote:
> > I know that a frozen array doesn't have to be
David Feuer wrote:
> I know that a frozen array doesn't have to be searched for elements in
> a younger generation, but how does it differ from an unfrozen array
> that hasn't been mutated since the last collection?
Frozen arrays are not put on the mutable list once they're clean
(meaning they
I know that a frozen array doesn't have to be searched for elements in
a younger generation, but how does it differ from an unfrozen array
that hasn't been mutated since the last collection?
David
___
Glasgow-haskell-users mailing list