##// END OF EJS Templates
rust-index: return variables systematic naming convention...
rust-index: return variables systematic naming convention To help knowing at a glance when a method is ready, making us more comofortable when we are close to the final removal of scaffolding, we introduce the systematic variable names `rust_res` and `c_res`. The goal of this series is to always return the formet. We take again the case of `pack_header` as example. Our personal opinion is to usually avoid such poor semantics as `res`, but usually accept it when it close to the actual return, which will be the case in most methods of this series. Also, the name can simply be dropped when we remove the scaffolding. To follow on the example, the body of `pack_header()` should become this in the final version: ``` let index = self.index(py).borrow(); let packed = index.pack_header(args.get_item(py, 0).extract(py)?); Ok(PyBytes::new(py, &packed).into_object()); ``` in these cases it is close to the actual return and will be removed at the end entirely.

File last commit:

r52014:34e0670c default
r52095:16d477bb default
Show More
Cargo.toml
4 lines | 97 B | application/toml | TOMLLexer
[workspace]
members = ["hg-core", "hg-cpython", "rhg"]
exclude = ["chg", "hgcli"]
resolver = "2"