Conversation
davidhewitt
left a comment
There was a problem hiding this comment.
Looks good other than the change on the .gitignore which I'm not convinced is necessary!
|
Build succeeded: |
|
I would prefer a |
I see that but it would be less obvious what's going on, and why the reverse can't be done. |
Actually this is a great point, I think the reverse could be implemented by However this also makes me notice another snag, which is naming convention. This is
|
|
The |
|
👍 for |
|
Pushed #3043 and I'll add separate PRs for other renaming and also |
3111: Rename sequence `.list()` and `.tuple()` to `.to_list()` and `.to_tuple()` r=adamreichold a=davidhewitt As agreed in #3042 (comment). The motivation is that it is an emerging Rust convention for `to_x` to mean "a non-consuming conversion to type x which has some (small) overhead". E.g. `to_string`, `to_owned`. Co-authored-by: David Hewitt <1939362+davidhewitt@users.noreply.github.com>
3111: Rename sequence `.list()` and `.tuple()` to `.to_list()` and `.to_tuple()` r=adamreichold a=davidhewitt As agreed in #3042 (comment). The motivation is that it is an emerging Rust convention for `to_x` to mean "a non-consuming conversion to type x which has some (small) overhead". E.g. `to_string`, `to_owned`. Co-authored-by: David Hewitt <1939362+davidhewitt@users.noreply.github.com>
From benchmarks, this is significantly faster than
PyTuple::new(py, the_list):