Rename "Properties" to "PropertySet"#1667
Rename "Properties" to "PropertySet"#1667PoignardAzur wants to merge 4 commits intolinebender:mainfrom
Conversation
Split `properties.rs` into (roughly) one file per struct/trait.
7a97942 to
e32bd42
Compare
Run cargo rdme
3fe1eeb to
a72b4f0
Compare
|
Given that this churns every open / pending change ... I'm not sure what the overall value / gain here is? Especially if we're talking about further substantial changes to properties... Help me understand? |
|
The short version is that I have other changes in the pipeline that define other types like "PropertyStack" or "PropertyArena" and that a "Properties" type is ambiguous compared to them. |
But feels a bit pre-mature because those changes wouldn't happen given some of the other stuff we want to talk about? |
|
Right, I was skipping some context there. We're still discussing when and how we'll integrate features from understory_properties and your experimental branch using them. I'd still like to merge this now. "Properties" is a bad name, and I'll still want to change it even (especially?) if we depend on understory_properties. I don't think this PR will make your work harder to integrate. |
xStrom
left a comment
There was a problem hiding this comment.
Yes, this will create churn all over the place. However, the changes themselves aren't bad. So let's just merge this sooner rather than later and move on and spend time discussing more substantive things.
Split `properties.rs` into (roughly) one file per struct/trait. This is a moving-and-renaming-only PR, with no behavior changes.
Split
properties.rsinto (roughly) one file per struct/trait.This is a moving-and-renaming-only PR, with no behavior changes.