Update to new zig version

[btipling]

Summary by CodeRabbit

• New Features

  • Enhanced consistency in type identifiers across mathematical operations, improving code readability and maintainability.

• Bug Fixes

  • Resolved type mismatch issues by standardizing type identifiers for vector and float comparisons, ensuring accurate error messaging.

• Documentation

  • Updated documentation to reflect changes in type naming conventions for better clarity.

• Chores

  • General housekeeping to align with new naming standards across multiple files without altering existing functionalities.

[coderabbitai]

Walkthrough

The changes involve a systematic renaming of type identifiers across multiple Zig files, transitioning from uppercase to lowercase naming conventions for types such as .Float, .ComptimeFloat, .Vector, and others. This adjustment enhances consistency in type identification while maintaining the core functionality of mathematical operations, comparisons, and vector manipulations. The overall structure and logic of the code remain intact, with no alterations to the signatures of public functions.

Changes

Files	Change Summary
src/foundations/math/float.zig	Modified type identifiers from .Float and .ComptimeFloat to .float and .comptime_float.
src/foundations/math/rotation.zig	Changed type identifiers from uppercase to lowercase for various types; no changes to function signatures.
src/foundations/math/vector.zig	Renamed type identifier from .Vector to .vector across multiple vector arithmetic functions.
src/foundations/rhi/rhi.zig	Updated type checks in defineStructData from .Vector and .Array to .vector and .array.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant MathFunctions
    participant VectorOperations

    User->>MathFunctions: Call equal(v, k, epsilon)
    MathFunctions->>MathFunctions: Compare v and k within epsilon
    MathFunctions-->>User: Return result

    User->>VectorOperations: Call add(v1, v2)
    VectorOperations->>VectorOperations: Perform addition of v1 and v2
    VectorOperations-->>User: Return result

Loading

Poem

🐇 In the land of code, where bunnies hop,
Type names now dance, they never stop!
From uppercase heights, they’ve come down low,
Clarity blooms, like flowers in a row.
With each little change, our joy takes flight,
Hooray for the code, all shiny and bright! 🌼

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 161ca6d and 2c8a885.

Files selected for processing (4)

• src/foundations/math/float.zig (1 hunks)
• src/foundations/math/rotation.zig (9 hunks)
• src/foundations/math/vector.zig (13 hunks)
• src/foundations/rhi/rhi.zig (1 hunks)

Files skipped from review due to trivial changes (2)

• src/foundations/math/float.zig
• src/foundations/math/rotation.zig

Additional comments not posted (14)

src/foundations/rhi/rhi.zig (1)

171-172: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

src/foundations/math/vector.zig (13)

31-34: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

66-69: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

90-93: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

114-117: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

139-140: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

156-156: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

173-173: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

188-188: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

220-221: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

332-334: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

356-358: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

375-376: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.

---

461-462: LGTM!

The changes are consistent with the new naming conventions. The logic of the function remains intact.