eggyal

When a move into a splitting prefix occurs, one could *at that commit*: * split the original file's history from the source into a subtree within a new orphan branch...

I can't speak to the cost, perhaps it's too great (albeit a feature that could be enabled only when desired, e.g. via command-line switch)... but surely only commits that involve...

In https://github.com/rust-lang/cargo/issues/5042#issuecomment-423695349, @kuviman wrote: > @nrc What if, in your example, change `./Cargo.toml` to simply > > ```toml > [workspace] > members = ["foo", "bar"] > ``` > > So,...

> I believe you always want your project to be nestable, the attribute is only needed since this would be a breaking change Agreed. Perhaps one could even configure `nestable`...

So if a potential parent workspace is found in the filesystem ancestry, but the child workspace neither appears amongst that potential parent workspace's `members` nor `exclude` fields, it is *assumed*...

> Isn't this already done by Cargo for regular packages to find the workspace and show the error you are talking about? Kind of. The search currently terminates once a...

> As a side note though, what is the rationale behind that error when a package "assumes" it is in the workspace when it is not? I've been looking into...

@goetas: Just because an XML type is _based_ on a primitive certainly doesn't mean that it should be mapped _onto_ a PHP primitive. On the contrary, better data typing would...

@goetas: Thank you for your detailed thoughts! Personally, I find the second version "cleaner" insofar as the PHP type system will prevent something that isn't a `tns:MiniInteger` being assigned to...

Short of adding such a method, could the guards at least expose a getter method for the slab/pool (currently I'm wrapping it up together with a reference thereto in a...