spease

@crumblingstatue For consistency, wouldn't "[cooldep.bin.dependencies]" make more sense as it keeps the most specific item on the left, getting more general as you go to the right?

I don't understand what you're saying. If a return type of String is specified, then the function contract is that it's returning an owned string object on the stack. In...

This would also be useful for a work project I'm working on.

How about using closure notation? Eg just like you’d unwrap_or_else(some_void_func) or unwrap_or_else(||1.0f64) This would be backwards compatible, consistent with existing Rust syntax, and even similar to the syntax you’d use...

Yes, I believe this is the same issue I'm currently having in some more complex code: ``` use serde::Deserialize; #[derive(Debug, Deserialize)] struct A { c: u64, } #[derive(Debug, Deserialize)] struct...

https://raw.githubusercontent.com/HUPO-PSI/mzML/master/schema/schema_1.1/mzML1.1.0.xsd The xml: and xs: in tag and attribute names would not parse (using Serde rename to set the exact name for a Rust struct member). After renaming with _...

@RReverser I'm accustomed to serde libraries using #[serde(rename)] for such cases rather than throwing out part of the identifier. That's what I've generally done with csv files for sure, but...

This seems like it should be an error rather than a panic. An application could recover from it.

Don’t know. I can work around it with buildPythonPackage and manually specifying pname etc. i think the error message is wrong and it does find it but it has an...

I tried it tonight, and I'm not sure. With your patch: One thing that seems to have changed is that I need to add a space to the requirements string...