Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update rust crate strum to 0.26.0 #1546

Merged
merged 1 commit into from
Jan 28, 2024
Merged

fix(deps): update rust crate strum to 0.26.0 #1546

merged 1 commit into from
Jan 28, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 28, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
strum dependencies minor 0.25.0 -> 0.26.0

Release Notes

Peternator7/strum (strum)

v0.26.0

Breaking Changes
  • The EnumVariantNames macro has been renamed VariantNames. The deprecation warning should steer you in
    the right direction for fixing the warning.
  • The Iterator struct generated by EnumIter now has new bounds on it. This shouldn't break code unless you manually
    added the implementation in your code.
  • Display now supports format strings using named fields in the enum variant. This should be a no-op for most code.
    However, if you were outputting a string like "Hello {field}", this will now be interpretted as a format string.
New features
  • The VariantArray macro has been added. This macro adds an associated constant VARIANTS to your enum. The constant
    is a &'static [Self] slice so that you can access all the variants of your enum. This only works on enums that only
    have unit variants.

    use strum::VariantArray;
    
    #[derive(Debug, VariantArray)]
    enum Color {
      Red,
      Blue,
      Green,
    }
    
    fn main() {
      println!("{:?}", Color::VARIANTS); // prints: ["Red", "Blue", "Green"]
    }
  • The EnumMap macro has been experimentally added. This macro adds a new type that stores an item for each variant
    of the enum. This is useful for storing a value for each variant of an enum. This is an experimental feature because
    I'm not convinced the current api surface area is correct.

    use strum::EnumMap;
    
    #[derive(Copy, Clone, Debug, EnumMap)]
    enum Color {
      Red,
      Blue,
      Green,
    }
    
    fn main() {
      let mut counts = ColorTable::filled(0);
      for color in &[Color::Red, Color::Red, Color::Green]] {
        counts[color] += 1;
      }
    
      assert_eq!(counts[Color::Red], 2);
      assert_eq!(counts[Color::Blue], 0);
      assert_eq!(counts[Color::Green], 1);
    }
  • Display has 2 new features:

    • the strum(prefix = "some_value") attribute on an enum now allows you to prepend a string onto every
      variant when you serialize it.

    • Custom to_string and serialize attributes now support string interopolation on serialization.

PR's Merged
  • #​322: avoid collisions on std::fmt::Debug
  • #​321: avoid conflicts with consecutive underscores.
  • #​314: add additional bounds to EnumIterator
  • #​311: add FusedIterator bounds to EnumIterator
  • #​297: New macro, add VariantArray
  • #​296: adds prefix attribute to To/From String macros.
  • #​294: use named enum fields in to_string macro.

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@jdx jdx merged commit 54fd770 into main Jan 28, 2024
9 checks passed
@jdx jdx deleted the renovate/strum-0.x branch January 28, 2024 15: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.

None yet

1 participant