tamer: (explicit_generic_args_with_impl_trait): Remove unstable feature flag
This was stabalized in Rust 1.63. I was waiting to be sure our build servers were updated properly before removing this (and they were, long ago).main
parent
ed8a2ce28a
commit
2a36bc4210
|
@ -56,7 +56,7 @@ test -n "$CARGO" || AC_MSG_ERROR([cargo not found])
|
|||
AC_SUBST([CARGO_FLAGS], "--frozen --offline")
|
||||
|
||||
# This is a nightly version at the time of writing
|
||||
rustc_ver_req=1.62
|
||||
rustc_ver_req=1.65
|
||||
|
||||
AC_CHECK_PROGS(RUSTC, [rustc])
|
||||
AC_MSG_CHECKING([rustc $RUST_TC version >= $rustc_ver_req])
|
||||
|
|
|
@ -43,13 +43,6 @@
|
|||
// this can be done more verbosely in the usual way,
|
||||
// or we can write our own version.
|
||||
#![feature(option_get_or_insert_default)]
|
||||
// This allows for e.g. `parse::<N>(foo)`,
|
||||
// where `fn parse<const N: T>(foo: impl Trait)`.
|
||||
// Rust devs wanted more time for public testing as of the time of writing
|
||||
// (March 2022).
|
||||
// We _could_ do without,
|
||||
// but this provides a nicer API.
|
||||
#![feature(explicit_generic_args_with_impl_trait)]
|
||||
// For `Try` and `FromResidual`,
|
||||
// allowing us to write our own `?`-compatible types.
|
||||
#![feature(try_trait_v2)]
|
||||
|
|
Loading…
Reference in New Issue