You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coming from the Haskell world, where there's only a single Doc type, the amount of abstraction and polymorphism in this library feels very daunting and complicated. It would be nice to document the motivation for these adaptations. For example, what's the difference between each allocator? What do the traits such as DocAllocator and DocPtr do and how do they help abstracting over allocators?
The text was updated successfully, but these errors were encountered:
poscat0x04
changed the title
Document the difference between each allocators
Document the difference between each allocator
Nov 16, 2023
Coming from the Haskell world, where there's only a single
Doc
type, the amount of abstraction and polymorphism in this library feels very daunting and complicated. It would be nice to document the motivation for these adaptations. For example, what's the difference between each allocator? What do the traits such asDocAllocator
andDocPtr
do and how do they help abstracting over allocators?The text was updated successfully, but these errors were encountered: