Threadwell

Recent Notes

  • DemetriSpanos

    Oct 06, 2026

    • archive
    • twitter
    • demetrispanos
  • NOTimothyLottes

    Oct 06, 2026

    • archive
    • twitter
    • notimothylottes
  • bonzajplc

    Oct 06, 2026

    • archive
    • twitter
    • bonzajplc
Home

❯

Archive

❯

Threads

❯

EricLengyel

❯

@bdiamand I'm not convinced that casting to force disjoint should be allowed, but if it had to be there, something similar to const_cast<>() would do it.

❯

@EricLengyel @bdiamand I imagine there might be some use cases for a disjoint_cast<>() for the implementation of custom allocators.

@EricLengyel @bdiamand I imagine there might be some use cases for a disjoint_cast<>() for the implementation of custom allocators.

Properties5
typearchive
sourcetwitter
date2019-12-05
tagsarchive, twitter, ericlengyel
description@EricLengyel @bdiamand I imagine there might be some use cases for a disjoint_cast<>() for the implementation of custom allocators.

Dec 05, 20191 min read

  • archive
  • twitter
  • ericlengyel

Source

  • URL: https://x.com/John_Ryland/status/1202585115307544578
  • Author: John_Ryland (@John_Ryland)
  • Posted: 2019-12-05 13:46:49

Branch

1/ @John_Ryland

@EricLengyel @bdiamand

I imagine there might be some use cases for a disjoint_cast<>() for the implementation of custom allocators.

Related

  • Spine: 2019-12-05-im-not-convinced-that-casting-to-force-disjoint

Graph View

  • Source
  • Branch
  • Related

Backlinks

  • @bdiamand I'm not convinced that casting to force disjoint should be allowed, but if it had to be there, something similar to const_cast<>() would do it.

Created with Quartz v5.0.0 © 2026

  • GitHub