Skip to content

Conversation

robertbastian
Copy link
Member

In policy and needed for #7065

@robertbastian robertbastian requested a review from a team as a code owner October 10, 2025 13:46
Copy link

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

@@ -46,7 +46,7 @@ where
}
}

// TODO(MSRV 1.83): Make this more infallible by calculating the required length,
// TODO(sffc): Make this more infallible by calculating the required length,
Copy link
Member Author

Choose a reason for hiding this comment

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

@sffc I don't know what this means

Copy link
Member

Choose a reason for hiding this comment

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

@robertbastian robertbastian merged commit f00ad5b into unicode-org:main Oct 13, 2025
31 checks passed
@robertbastian robertbastian deleted the 83 branch October 13, 2025 08:35
@sffc sffc added the discuss-priority Discuss at the next ICU4X meeting label Oct 14, 2025
@sffc
Copy link
Member

sffc commented Oct 14, 2025

This is in policy for ICU4X component crates. But, after releasing new versions of everything in 2.0, I think we should by default keep utility crates on the lower MSRV until the individual utils crates need the bump.

@sffc sffc mentioned this pull request Oct 14, 2025
@sffc
Copy link
Member

sffc commented Oct 16, 2025

Proposal:

  • Set MSRV 1.82 in the Cargo.toml of all utils crates
  • Allow individual utils crates to opt for a different MSRV when they need a new feature
  • Utils crates can adopt the N-6 MSRV without needing any justification if they are undergoing a major release
  • This policy has no impact on ICU component crates

@sffc
Copy link
Member

sffc commented Oct 16, 2025

WG Discussion on the above policy (#7066 (comment)):

  • @Manishearth Seems fine. Let's update the policy to say that utils crates don't get automatically bumped, but can be bumped to the ICU4X MSRV without approval if they need the version for any reason.
  • @zbranicki In large organizations, Rust versions don't get bumped often, so I'm happy with policies to strengthen low MSRV requirements.

Conclusion: yep, + policy edit

LGTM: @Manishearth @sffc @zbraniecki

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

discuss-priority Discuss at the next ICU4X meeting

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants