You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ICU4X Technical Committee is happy to announce [ICU4X](https://github.com/unicode-org/icu4x) 2.2, an update to our modular, portable, and secure i18n library.
Important changes in ICU4X 2.2 include:
1. **Latest i18n data:** This release includes an update to [CLDR 48.2](https://cldr.unicode.org/downloads/cldr-48#482-changes) and support for TZDB 2026a.
2. **New and improved `icu_calendar`:** This release contains new APIs in `icu_calendar`, as well as some behavior changes in icu_calendar; see the migration notes section.
1. Stable datetime arithmetic: It is now possible to to add and subtract dates via `date.try_add_with_options()` and `date.try_until_with_options()`.
2. More flexible date construction: The new `Date::try_from_fields()` API allows constructing dates from all kinds of constituent data: extended years, era years, ordinal months, month codes, etc., and supports different kinds of overflow handling.
3. Typed months: The new `Month` type replaces month codes in a type safe way. `Date::try_from_codes()` has been replaced with `Date::try_new()` which uses these better types. Various calendar-specific constructors for lunisolar calendars have also been refreshed.
4. Experimental third-party crate integration: We now support converting from and formatting types from the `jiff`, `chrono`, and `time` crates. See `icu_datetime::input::third_party`. We’re not yet sure if these integrations should live in ICU4X, in the third party crates, or some adapter crate, and are [open to feedback](https://github.com/unicode-org/icu4x/issues/7845)!
3. Experimental Kotlin Bindings: We now have Kotlin bindings for ICU4X (found under `ffi/mvn`), with the same set of supported APIs as our other cross-language bindings.
4. Experimental features:
1. Display names: Adds new internal data layout exposed via RegionDisplayName and ScriptDisplayName APIs. The old data layout, optimized for loading multiple names at once, is moved into the multi module. Please share feedback on our [tracking issue](https://github.com/unicode-org/icu4x/issues/7824).
2. Compact decimal formatter: Please share feedback in preparation for stabilization in a future release.
3. ML segmentation: Initial code for RAdaBoost word segmenter for Chinese and CNN word segmenter for Thai.
5. Unstable Cargo feature: Replaced the "experimental" Cargo feature with an "unstable" Cargo feature.
6. Better hour cycles: Adds support for Clock12 and Clock24 in datetime formatting.
### Migration Notes
1. The `JapaneseExtended` calendar has been deprecated. CLDR removed the pre-Meiji eras because no implementation correctly implemented them. Clients of pre-Meiji eras are encouraged to comment on [CLDR-11400](https://unicode-org.atlassian.net/browse/CLDR-11400) and potentially write a custom `east_asian_traditional::Rules` implementation of the pre-Meiji lunisolar Japanese calendar.
2. `Hijri<AstronomicalSimulation>` has also been deprecated. It previously returned estimates of the Hijri calendar based on simulations published by Reingold et al. To restore this behavior, write a custom `hijri::Rules` implementation using calendrical_calculations.
[See the full changelog for more information](https://github.com/unicode-org/icu4x/blob/main/CHANGELOG.md#icu4x-22)
The ICU4X Technical Committee is happy to announce [ICU4X](https://github.com/unicode-org/icu4x) 2.2, an update to our modular, portable, and secure i18n library.
Important changes in ICU4X 2.2 include:
1. **Latest i18n data:** This release includes an update to [CLDR 48.2](https://cldr.unicode.org/downloads/cldr-48#482-changes) and support for TZDB 2026a.
2. **New and improved `icu_calendar`:** This release contains new APIs in `icu_calendar`, as well as some behavior changes in icu_calendar; see the migration notes section.
1. Stable datetime arithmetic: It is now possible to to add and subtract dates via `date.try_add_with_options()` and `date.try_until_with_options()`.
2. More flexible date construction: The new `Date::try_from_fields()` API allows constructing dates from all kinds of constituent data: extended years, era years, ordinal months, month codes, etc., and supports different kinds of overflow handling.
3. Typed months: The new `Month` type replaces month codes in a type safe way. `Date::try_from_codes()` has been replaced with `Date::try_new()` which uses these better types. Various calendar-specific constructors for lunisolar calendars have also been refreshed.
4. Experimental third-party crate integration: We now support converting from and formatting types from the `jiff`, `chrono`, and `time` crates. See `icu_datetime::input::third_party`. We’re not yet sure if these integrations should live in ICU4X, in the third party crates, or some adapter crate, and are [open to feedback](https://github.com/unicode-org/icu4x/issues/7845)!
3. Experimental Kotlin Bindings: We now have Kotlin bindings for ICU4X (found under `ffi/mvn`), with the same set of supported APIs as our other cross-language bindings.
4. Experimental features:
1. Display names: Adds new internal data layout exposed via RegionDisplayName and ScriptDisplayName APIs. The old data layout, optimized for loading multiple names at once, is moved into the multi module. Please share feedback on our [tracking issue](https://github.com/unicode-org/icu4x/issues/7824).
2. Compact decimal formatter: Please share feedback in preparation for stabilization in a future release.
3. ML segmentation: Initial code for RAdaBoost word segmenter for Chinese and CNN word segmenter for Thai.
5. Unstable Cargo feature: Replaced the "experimental" Cargo feature with an "unstable" Cargo feature.
6. Better hour cycles: Adds support for Clock12 and Clock24 in datetime formatting.
### Migration Notes
1. The `JapaneseExtended` calendar has been deprecated. CLDR removed the pre-Meiji eras because no implementation correctly implemented them. Clients of pre-Meiji eras are encouraged to comment on [CLDR-11400](https://unicode-org.atlassian.net/browse/CLDR-11400) and potentially write a custom `east_asian_traditional::Rules` implementation of the pre-Meiji lunisolar Japanese calendar.
2. `Hijri<AstronomicalSimulation>` has also been deprecated. It previously returned estimates of the Hijri calendar based on simulations published by Reingold et al. To restore this behavior, write a custom `hijri::Rules` implementation using calendrical_calculations.
[See the full changelog for more information](https://github.com/unicode-org/icu4x/blob/main/CHANGELOG.md#icu4x-22)
The ICU4X Technical Committee is happy to announce [ICU4X](https://github.com/unicode-org/icu4x) 2.2, an update to our modular, portable, and secure i18n library.
Important changes in ICU4X 2.2 include:
1. **Latest i18n data:** This release includes an update to [CLDR 48.2](https://cldr.unicode.org/downloads/cldr-48#482-changes) and support for TZDB 2026a.
2. **New and improved `icu_calendar`:** This release contains new APIs in `icu_calendar`, as well as some behavior changes in icu_calendar; see the migration notes section.
1. Stable datetime arithmetic: It is now possible to to add and subtract dates via `date.try_add_with_options()` and `date.try_until_with_options()`.
2. More flexible date construction: The new `Date::try_from_fields()` API allows constructing dates from all kinds of constituent data: extended years, era years, ordinal months, month codes, etc., and supports different kinds of overflow handling.
3. Typed months: The new `Month` type replaces month codes in a type safe way. `Date::try_from_codes()` has been replaced with `Date::try_new()` which uses these better types. Various calendar-specific constructors for lunisolar calendars have also been refreshed.
4. Experimental third-party crate integration: We now support converting from and formatting types from the `jiff`, `chrono`, and `time` crates. See `icu_datetime::input::third_party`. We’re not yet sure if these integrations should live in ICU4X, in the third party crates, or some adapter crate, and are [open to feedback](https://github.com/unicode-org/icu4x/issues/7845)!
3. Experimental Kotlin Bindings: We now have Kotlin bindings for ICU4X (found under `ffi/mvn`), with the same set of supported APIs as our other cross-language bindings.
4. Experimental features:
1. Display names: Adds new internal data layout exposed via RegionDisplayName and ScriptDisplayName APIs. The old data layout, optimized for loading multiple names at once, is moved into the multi module. Please share feedback on our [tracking issue](https://github.com/unicode-org/icu4x/issues/7824).
2. Compact decimal formatter: Please share feedback in preparation for stabilization in a future release.
3. ML segmentation: Initial code for RAdaBoost word segmenter for Chinese and CNN word segmenter for Thai.
5. Unstable Cargo feature: Replaced the "experimental" Cargo feature with an "unstable" Cargo feature.
6. Better hour cycles: Adds support for Clock12 and Clock24 in datetime formatting.
### Migration Notes
1. The `JapaneseExtended` calendar has been deprecated. CLDR removed the pre-Meiji eras because no implementation correctly implemented them. Clients of pre-Meiji eras are encouraged to comment on [CLDR-11400](https://unicode-org.atlassian.net/browse/CLDR-11400) and potentially write a custom `east_asian_traditional::Rules` implementation of the pre-Meiji lunisolar Japanese calendar.
2. `Hijri<AstronomicalSimulation>` has also been deprecated. It previously returned estimates of the Hijri calendar based on simulations published by Reingold et al. To restore this behavior, write a custom `hijri::Rules` implementation using calendrical_calculations.
[See the full changelog for more information](https://github.com/unicode-org/icu4x/blob/main/CHANGELOG.md#icu4x-22)
The ICU4X Technical Committee is happy to announce [ICU4X](https://github.com/unicode-org/icu4x) 2.2, an update to our modular, portable, and secure i18n library.
Important changes in ICU4X 2.2 include:
1. **Latest i18n data:** This release includes an update to [CLDR 48.2](https://cldr.unicode.org/downloads/cldr-48#482-changes) and support for TZDB 2026a.
2. **New and improved `icu_calendar`:** This release contains new APIs in `icu_calendar`, as well as some behavior changes in icu_calendar; see the migration notes section.
1. Stable datetime arithmetic: It is now possible to to add and subtract dates via `date.try_add_with_options()` and `date.try_until_with_options()`.
2. More flexible date construction: The new `Date::try_from_fields()` API allows constructing dates from all kinds of constituent data: extended years, era years, ordinal months, month codes, etc., and supports different kinds of overflow handling.
3. Typed months: The new `Month` type replaces month codes in a type safe way. `Date::try_from_codes()` has been replaced with `Date::try_new()` which uses these better types. Various calendar-specific constructors for lunisolar calendars have also been refreshed.
4. Experimental third-party crate integration: We now support converting from and formatting types from the `jiff`, `chrono`, and `time` crates. See `icu_datetime::input::third_party`. We’re not yet sure if these integrations should live in ICU4X, in the third party crates, or some adapter crate, and are [open to feedback](https://github.com/unicode-org/icu4x/issues/7845)!
3. Experimental Kotlin Bindings: We now have Kotlin bindings for ICU4X (found under `ffi/mvn`), with the same set of supported APIs as our other cross-language bindings.
4. Experimental features:
1. Display names: Adds new internal data layout exposed via RegionDisplayName and ScriptDisplayName APIs. The old data layout, optimized for loading multiple names at once, is moved into the multi module. Please share feedback on our [tracking issue](https://github.com/unicode-org/icu4x/issues/7824).
2. Compact decimal formatter: Please share feedback in preparation for stabilization in a future release.
3. ML segmentation: Initial code for RAdaBoost word segmenter for Chinese and CNN word segmenter for Thai.
5. Unstable Cargo feature: Replaced the "experimental" Cargo feature with an "unstable" Cargo feature.
6. Better hour cycles: Adds support for Clock12 and Clock24 in datetime formatting.
### Migration Notes
1. The `JapaneseExtended` calendar has been deprecated. CLDR removed the pre-Meiji eras because no implementation correctly implemented them. Clients of pre-Meiji eras are encouraged to comment on [CLDR-11400](https://unicode-org.atlassian.net/browse/CLDR-11400) and potentially write a custom `east_asian_traditional::Rules` implementation of the pre-Meiji lunisolar Japanese calendar.
2. `Hijri<AstronomicalSimulation>` has also been deprecated. It previously returned estimates of the Hijri calendar based on simulations published by Reingold et al. To restore this behavior, write a custom `hijri::Rules` implementation using calendrical_calculations.
[See the full changelog for more information](https://github.com/unicode-org/icu4x/blob/main/CHANGELOG.md#icu4x-22)
The ICU4X Technical Committee is happy to announce [ICU4X](https://github.com/unicode-org/icu4x) 2.2, an update to our modular, portable, and secure i18n library.
Important changes in ICU4X 2.2 include:
1. **Latest i18n data:** This release includes an update to [CLDR 48.2](https://cldr.unicode.org/downloads/cldr-48#482-changes) and support for TZDB 2026a.
2. **New and improved `icu_calendar`:** This release contains new APIs in `icu_calendar`, as well as some behavior changes in icu_calendar; see the migration notes section.
1. Stable datetime arithmetic: It is now possible to to add and subtract dates via `date.try_add_with_options()` and `date.try_until_with_options()`.
2. More flexible date construction: The new `Date::try_from_fields()` API allows constructing dates from all kinds of constituent data: extended years, era years, ordinal months, month codes, etc., and supports different kinds of overflow handling.
3. Typed months: The new `Month` type replaces month codes in a type safe way. `Date::try_from_codes()` has been replaced with `Date::try_new()` which uses these better types. Various calendar-specific constructors for lunisolar calendars have also been refreshed.
4. Experimental third-party crate integration: We now support converting from and formatting types from the `jiff`, `chrono`, and `time` crates. See `icu_datetime::input::third_party`. We’re not yet sure if these integrations should live in ICU4X, in the third party crates, or some adapter crate, and are [open to feedback](https://github.com/unicode-org/icu4x/issues/7845)!
3. Experimental Kotlin Bindings: We now have Kotlin bindings for ICU4X (found under `ffi/mvn`), with the same set of supported APIs as our other cross-language bindings.
4. Experimental features:
1. Display names: Adds new internal data layout exposed via RegionDisplayName and ScriptDisplayName APIs. The old data layout, optimized for loading multiple names at once, is moved into the multi module. Please share feedback on our [tracking issue](https://github.com/unicode-org/icu4x/issues/7824).
2. Compact decimal formatter: Please share feedback in preparation for stabilization in a future release.
3. ML segmentation: Initial code for RAdaBoost word segmenter for Chinese and CNN word segmenter for Thai.
5. Unstable Cargo feature: Replaced the "experimental" Cargo feature with an "unstable" Cargo feature.
6. Better hour cycles: Adds support for Clock12 and Clock24 in datetime formatting.
### Migration Notes
1. The `JapaneseExtended` calendar has been deprecated. CLDR removed the pre-Meiji eras because no implementation correctly implemented them. Clients of pre-Meiji eras are encouraged to comment on [CLDR-11400](https://unicode-org.atlassian.net/browse/CLDR-11400) and potentially write a custom `east_asian_traditional::Rules` implementation of the pre-Meiji lunisolar Japanese calendar.
2. `Hijri<AstronomicalSimulation>` has also been deprecated. It previously returned estimates of the Hijri calendar based on simulations published by Reingold et al. To restore this behavior, write a custom `hijri::Rules` implementation using calendrical_calculations.
[See the full changelog for more information](https://github.com/unicode-org/icu4x/blob/main/CHANGELOG.md#icu4x-22)
The ICU4X Technical Committee is happy to announce [ICU4X](https://github.com/unicode-org/icu4x) 2.2, an update to our modular, portable, and secure i18n library.
Important changes in ICU4X 2.2 include:
1. **Latest i18n data:** This release includes an update to [CLDR 48.2](https://cldr.unicode.org/downloads/cldr-48#482-changes) and support for TZDB 2026a.
2. **New and improved `icu_calendar`:** This release contains new APIs in `icu_calendar`, as well as some behavior changes in icu_calendar; see the migration notes section.
1. Stable datetime arithmetic: It is now possible to to add and subtract dates via `date.try_add_with_options()` and `date.try_until_with_options()`.
2. More flexible date construction: The new `Date::try_from_fields()` API allows constructing dates from all kinds of constituent data: extended years, era years, ordinal months, month codes, etc., and supports different kinds of overflow handling.
3. Typed months: The new `Month` type replaces month codes in a type safe way. `Date::try_from_codes()` has been replaced with `Date::try_new()` which uses these better types. Various calendar-specific constructors for lunisolar calendars have also been refreshed.
4. Experimental third-party crate integration: We now support converting from and formatting types from the `jiff`, `chrono`, and `time` crates. See `icu_datetime::input::third_party`. We’re not yet sure if these integrations should live in ICU4X, in the third party crates, or some adapter crate, and are [open to feedback](https://github.com/unicode-org/icu4x/issues/7845)!
3. Experimental Kotlin Bindings: We now have Kotlin bindings for ICU4X (found under `ffi/mvn`), with the same set of supported APIs as our other cross-language bindings.
4. Experimental features:
1. Display names: Adds new internal data layout exposed via RegionDisplayName and ScriptDisplayName APIs. The old data layout, optimized for loading multiple names at once, is moved into the multi module. Please share feedback on our [tracking issue](https://github.com/unicode-org/icu4x/issues/7824).
2. Compact decimal formatter: Please share feedback in preparation for stabilization in a future release.
3. ML segmentation: Initial code for RAdaBoost word segmenter for Chinese and CNN word segmenter for Thai.
5. Unstable Cargo feature: Replaced the "experimental" Cargo feature with an "unstable" Cargo feature.
6. Better hour cycles: Adds support for Clock12 and Clock24 in datetime formatting.
### Migration Notes
1. The `JapaneseExtended` calendar has been deprecated. CLDR removed the pre-Meiji eras because no implementation correctly implemented them. Clients of pre-Meiji eras are encouraged to comment on [CLDR-11400](https://unicode-org.atlassian.net/browse/CLDR-11400) and potentially write a custom `east_asian_traditional::Rules` implementation of the pre-Meiji lunisolar Japanese calendar.
2. `Hijri<AstronomicalSimulation>` has also been deprecated. It previously returned estimates of the Hijri calendar based on simulations published by Reingold et al. To restore this behavior, write a custom `hijri::Rules` implementation using calendrical_calculations.
[See the full changelog for more information](https://github.com/unicode-org/icu4x/blob/main/CHANGELOG.md#icu4x-22)
The ICU4X Technical Committee is happy to announce [ICU4X](https://github.com/unicode-org/icu4x) 2.2, an update to our modular, portable, and secure i18n library.
Important changes in ICU4X 2.2 include:
1. **Latest i18n data:** This release includes an update to [CLDR 48.2](https://cldr.unicode.org/downloads/cldr-48#482-changes) and support for TZDB 2026a.
2. **New and improved `icu_calendar`:** This release contains new APIs in `icu_calendar`, as well as some behavior changes in icu_calendar; see the migration notes section.
1. Stable datetime arithmetic: It is now possible to to add and subtract dates via `date.try_add_with_options()` and `date.try_until_with_options()`.
2. More flexible date construction: The new `Date::try_from_fields()` API allows constructing dates from all kinds of constituent data: extended years, era years, ordinal months, month codes, etc., and supports different kinds of overflow handling.
3. Typed months: The new `Month` type replaces month codes in a type safe way. `Date::try_from_codes()` has been replaced with `Date::try_new()` which uses these better types. Various calendar-specific constructors for lunisolar calendars have also been refreshed.
4. Experimental third-party crate integration: We now support converting from and formatting types from the `jiff`, `chrono`, and `time` crates. See `icu_datetime::input::third_party`. We’re not yet sure if these integrations should live in ICU4X, in the third party crates, or some adapter crate, and are [open to feedback](https://github.com/unicode-org/icu4x/issues/7845)!
3. Experimental Kotlin Bindings: We now have Kotlin bindings for ICU4X (found under `ffi/mvn`), with the same set of supported APIs as our other cross-language bindings.
4. Experimental features:
1. Display names: Adds new internal data layout exposed via RegionDisplayName and ScriptDisplayName APIs. The old data layout, optimized for loading multiple names at once, is moved into the multi module. Please share feedback on our [tracking issue](https://github.com/unicode-org/icu4x/issues/7824).
2. Compact decimal formatter: Please share feedback in preparation for stabilization in a future release.
3. ML segmentation: Initial code for RAdaBoost word segmenter for Chinese and CNN word segmenter for Thai.
5. Unstable Cargo feature: Replaced the "experimental" Cargo feature with an "unstable" Cargo feature.
6. Better hour cycles: Adds support for Clock12 and Clock24 in datetime formatting.
### Migration Notes
1. The `JapaneseExtended` calendar has been deprecated. CLDR removed the pre-Meiji eras because no implementation correctly implemented them. Clients of pre-Meiji eras are encouraged to comment on [CLDR-11400](https://unicode-org.atlassian.net/browse/CLDR-11400) and potentially write a custom `east_asian_traditional::Rules` implementation of the pre-Meiji lunisolar Japanese calendar.
2. `Hijri<AstronomicalSimulation>` has also been deprecated. It previously returned estimates of the Hijri calendar based on simulations published by Reingold et al. To restore this behavior, write a custom `hijri::Rules` implementation using calendrical_calculations.
[See the full changelog for more information](https://github.com/unicode-org/icu4x/blob/main/CHANGELOG.md#icu4x-22)
### MSRV
This release increases the MSRV of `libc` to 1.65. With this update, you can now always use the
`core::ffi::c_*` types with `libc` definitions, since `libc` has been changed to reexport from
`core` rather than redefining them. (This _usually_ worked before but had edge cases.)
([#4972](https://github.com/rust-lang/libc/pull/4972))
### Added
- BSD: Add `IP_MINTTL` to bsd ([#5026](https://github.com/rust-lang/libc/pull/5026))
- Cygwin: Add `TIOCM_DSR` ([#5031](https://github.com/rust-lang/libc/pull/5031))
- FreeBSD: Added `xfile` structe and file descriptor types ([#5002](https://github.com/rust-lang/libc/pull/5002))
- Linux: Add CAN netlink bindings ([#5011](https://github.com/rust-lang/libc/pull/5011))
- Linux: Add `struct ethhdr` ([#4239](https://github.com/rust-lang/libc/pull/4239))
- Linux: Add `struct ifinfomsg` ([#5012](https://github.com/rust-lang/libc/pull/5012))
- Linux: Define `max_align_t` for riscv64 ([#5029](https://github.com/rust-lang/libc/pull/5029))
- NetBSD: Add missing `CLOCK_` constants ([#5020](https://github.com/rust-lang/libc/pull/5020))
- NuttX: Add `_SC_HOST_NAME_MAX` ([#5004](https://github.com/rust-lang/libc/pull/5004))
- VxWorks: Add `flock` and `F_*LCK` constants ([#4043](https://github.com/rust-lang/libc/pull/4043))
- WASI: Add all `_SC_*` sysconf constants ([#5023](https://github.com/rust-lang/libc/pull/5023))
### Deprecated
The remaining fixed-width integer aliases, `__uint128_t`, `__uint128`, `__int128_t`, and `__int128`,
have been deprecated. Use `i128` and `u128` instead. ([#4343](https://github.com/rust-lang/libc/pull/4343))
### Fixed
- **breaking** Redox: Fix signal action constant types ([#5009](https://github.com/rust-lang/libc/pull/5009))
- EspIDF: Correct the value of `DT_*` constants ([#5034](https://github.com/rust-lang/libc/pull/5034))
- Redox: Fix locale values and add `RTLD_NOLOAD`, some TCP constants ([#5025](https://github.com/rust-lang/libc/pull/5025))
- Various: Use `Padding::new(<zeroed>)` rather than `Padding::uninit()` ([#5036](https://github.com/rust-lang/libc/pull/5036))
### Changed
- **potentially breaking** Linux: Add new fields to `struct ptrace_syscall_info` ([#4966](https://github.com/rust-lang/libc/pull/4966))
- Re-export `core::ffi` integer types rather than redefining ([#5015](https://github.com/rust-lang/libc/pull/5015))
- Redox: Update `F_DUPFD`, `IP`, and `TCP` constants to match relibc ([#4990](https://github.com/rust-lang/libc/pull/4990))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
botbotdependenciesPull requests that update a dependency file
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.