Message381827
| Author | BTaskaya |
|---|---|
| Recipients | BTaskaya, Mark.Shannon, christian.heimes, josh.r, mark.dickinson, pablogsal, rhettinger, serhiy.storchaka |
| Date | 2020-11-25.12:39:39 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1606307979.66.0.0126785398785.issue42454@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> What are the potential benefits or drawbacks for the user? The only potential drawback that I can see is that it prevents you from distinguishing a sequence from mapping by 'accidentally' passing a slice. The major benefit for users is that they will have a decent speed up on their slice access. Other than that, I can think of some scenarios where the slice objects can be usable. One thing that I just came up with is this example (https://gist.github.com/isidentical/a799c4ae5c318bb7ac1a9f101cb709c7). I don't claim that we are implementing this to support these kinds of obscure cases, but it doesn't hurt anyone (beside maybe become a little bit confusing for a second) and doesn't look odd when used with a decent purpose. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2020-11-25 12:39:39 | BTaskaya | set | recipients: + BTaskaya, rhettinger, mark.dickinson, christian.heimes, Mark.Shannon, serhiy.storchaka, josh.r, pablogsal |
| 2020-11-25 12:39:39 | BTaskaya | set | messageid: <1606307979.66.0.0126785398785.issue42454@roundup.psfhosted.org> |
| 2020-11-25 12:39:39 | BTaskaya | link | issue42454 messages |
| 2020-11-25 12:39:39 | BTaskaya | create | |