Seth
Seth
I agree that mojo stdlib should have a cohesive and consistent design. I'd love to wholesale adopt https://rust-lang.github.io/api-guidelines/about.html. Possibly this issue should be retargeted at creating an API design spec...
That's a great idea! Thanks for the PR, I'd very much like to get this in.
WIP of updated tests: https://github.com/sstadick/max/pull/1 (diff is vs this PR)
@JoeLoser I've added to the tests, and better labeled what is there, as well as added a few details to the docs.
I saw it in 25.3, thanks for getting it in that release!
I ran into this when updating some code to latest mojo. The fix was specifying the width parameter: ``` from tensor import Tensor from utils.index import Index fn test(): var...
Agreed! This would be great to have. I'm not sure I'll be adding it myself in the near future just due to time constraints. But I'd be happy to have...
I'd be happy to add some benchmarks in a follow up PR. I did some [here](https://forum.modular.com/t/pack-bits-inside-of-vectorize-fails-constraint-check/1384/11?u=duck_tape) but they won't translate to the stdlib.
Less minimal example: ```python from runtime.asyncrt import DeviceContextPtr, TaskGroup, parallelism_level from os.atomic import Atomic from time import sleep fn run[ thread_a_part1: fn () capturing -> Int, thread_a_part2: fn () capturing...
I believe this is because the bam header isn't up to date with the refs used? Could you share a small bam file / the refs your'e using? Sorry for...