You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just used range to find the first index which satisfies some condition relating to the next member of the list.
I had to use .toInt() twice, to convert the num instances to ints.
How about adding an "irange" and "icount" functions, which would do the same thing but with ints?
If I send a pull request with that, will it be considered?
Thanks,
Noam
The text was updated successfully, but these errors were encountered:
Since only the types would differ, I think the right approach would probably to make range generic. That would allow for either approach. That would rely on implicit type deduction for backward compatibility, so we'd want to test on the internal codebase, but that seems reasonable to me.
Hi,
I just used range to find the first index which satisfies some condition relating to the next member of the list.
I had to use .toInt() twice, to convert the num instances to ints.
How about adding an "irange" and "icount" functions, which would do the same thing but with ints?
If I send a pull request with that, will it be considered?
Thanks,
Noam
The text was updated successfully, but these errors were encountered: