Resource Polymorphism · HackerPapers discussions

Resource Polymorphism — mentioned by rwmj

Thu, 23 Dec 2021 08:53:21 GMT

Garbage collection and controlled object lifetimes are important and orthogonal concerns. You can have both at the same time. C# for instance lets you add a Dispose() method for the times when you want to free the resources now. There are even ways to ensure statically that objects aren't used after the close/dispose is called. (Of which I would find the paper, but my google-fu is failing me right now ... https://okmij.org/ftp/Haskell/regions.html and https://arxiv.org/abs/1803.02796 I think)

Paper and discussion history. A mention is not an endorsement.

Resource Polymorphism — mentioned by Ericson2314

Sat, 20 Jun 2020 14:51:08 GMT

Yes to almost all of that. The proposal process has exhausted me, but I suppose I will write it again, since your questions there serve as excellent section headings :). > Do you think the feature is not going to be very useful in a practical setting? Yes. For one example, you cannot write anything like `malloc :: Word -> LinearPtr Void`. With, `malloc :: Word -o Ptr Void`, since Word is not duplicable, `Ptr Void` would be. The "solution" is to CPS everything, which is pointed out in the paper and they say it's OK cause some big honking monad can take care of that, but I don't buy it, and I…

Paper and discussion history. A mention is not an endorsement.

Resource Polymorphism — mentioned by Ericson2314

Fri, 06 Dec 2019 05:53:59 GMT

https://arxiv.org/abs/1803.02796 has a good intro referencing other work. The paper doesn't go into much detail on the borrow checking side of things, but that author is both thoroughly steeped in the linear types research tradition and knows Rust and mentions it a bunch. The fact that that paper talks about the affine types far more than the lifetimes obliquely illustrates my point in my view, I'm not sure if it's been stated more directly. https://gallium.inria.fr/~fpottier/slides/fpottier-2007-05-l... has some nice history. It wish there is a newer version for things that have been…

Paper and discussion history. A mention is not an endorsement.

Resource Polymorphism — mentioned by zozbot123

Mon, 31 Dec 2018 13:44:17 GMT

> and all GC enabled system programming languages do offer multiple ways to manage memory. Since "GC-enabled system programming languages" is an oxymoron, a claim about what such languages may or may not include is just not very useful. But it's definitely the case that properly combining, e.g. "traced GC memory references" and RAII including deterministic deallocation for resources is still a matter of ongoing research, e.g. https://arxiv.org/abs/1803.02796 That may or may not pan out in the future, as may other things such as pluggable, lightweight GC for a subset of memory objects, etc.…

Paper and discussion history. A mention is not an endorsement.

Resource Polymorphism — HN submission

Thu, 15 Mar 2018 23:15:34 GMT

Rust-style resource management in OCaml

131 points; 57 discussion replies on HN. Paper and source history. A submission is not an endorsement.