Bikeshed: other names for "Kind" in "Allocator" API

pnkfelix · 2015-12-20T14:54:07.923Z

RFC PR 1398 proposes a trait for user-defined allocators. As part of the API, it proposes a helper type, named Kind, for describing the layout of a block of memory.

People have pointed out that the word “Kind” may end up confusing things if/when Rust adds support for “higher kinded types” (HKT).

@glaeboerhl has suggested that we rename “Kind” to something else, and proposed “Shape”:

github.com/rust-lang/rfcs

Allocators, take III

by pnkfelix on 06:39PM - 06 Dec 15

38 commits changed 1 files with 2198 additions and 0 deletions.

So, what do people think? I have no personal stake in the word “Kind”; I could also imagine other words. So here’s a quick list:

“Kind”
“Shape”
“Layout”
“BlockConstraints”

Thoughts?

yigal100 · 2015-12-21T10:42:06.711Z

layout sounds the most descriptive for the intended semantics. Especially if it’ll reside in a suitable path such as std::memory::Layout.

glaebhoerl · 2015-12-21T13:18:39.032Z

I think Layout sounds fine too. Another idea might be Repr.

kstep · 2015-12-25T16:38:37.105Z

For me Repr reminds of Python’s __repr__ and is strongly associated with Rust’s Debug trait. Layout sounds pretty fine for me in this context.

mcpherrinm · 2015-12-29T00:52:59.522Z

For reference, This is the API we’re bikeshedding.

I would name this Layout. The only misinterpretation I can think of is to assume it’s something to do with where in the address space it is, but the (size, alignment) members make it pretty clear what it’s for.

I’d be fine with Shape too, but it feels a little unnatural to me: It’s not a word I’d use when talking about allocators.

pnkfelix · 2019-03-25T08:25:36.214Z

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.