Skip to content

Conversation

@LaurenzV
Copy link
Contributor

While I know we have decided to try to mostly stick to released versions, having vello_cpu point to the current main of fearless_simd will make it easier to benchmark some upcoming changes.

Copy link
Contributor

@valadaptive valadaptive left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Is there a particular release schedule for vello_cpu or vello_hybrid that will require us to cut a release of fearless_simd?

@grebmeg
Copy link
Collaborator

grebmeg commented Dec 16, 2025

Would you be able to publish vello_cpu now if it has a git dependency? From what I’m reading in the docs, although they aren’t very explicit, the manifest for such a publish would be rejected.

Also, why not publish fearless_simd and use the published version here instead?

@valadaptive
Copy link
Contributor

Would you be able to publish vello_cpu now if it has a git dependency? From what I’m reading in the docs, although they aren’t very explicit, the manifest for such a publish would be rejected.

I believe we would not.

Also, why not publish fearless_simd and use the published version here instead?

We want to benchmark some upcoming changes that should make it in before the next release.

@LaurenzV
Copy link
Contributor Author

I mean, I wouldn’t mind making another release of fearless_simd now before we make further changes. I can try to do it today.

@LaurenzV LaurenzV marked this pull request as draft December 21, 2025 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants