pub trait FromStr: Sized {
type Err;
// Required method
fn from_str(s: &str) -> Result<Self, Self::Err>;
}Expand description
Parse a value from a string
FromStr’s from_str method is often used implicitly, through
str’s parse method. See parse’s documentation for examples.
FromStr does not have a lifetime parameter, and so you can only parse types
that do not contain a lifetime parameter themselves. In other words, you can
parse an i32 with FromStr, but not a &i32. You can parse a struct that
contains an i32, but not one that contains an &i32.
§Input format and round-tripping
The input format expected by a type’s FromStr implementation depends on the type. Check the
type’s documentation for the input formats it knows how to parse. Note that the input format of
a type’s FromStr implementation might not necessarily accept the output format of its
Display implementation, and even if it does, the Display implementation may not be lossless
so the round-trip may lose information.
However, if a type has a lossless Display implementation whose output is meant to be
conveniently machine-parseable and not just meant for human consumption, then the type may wish
to accept the same format in FromStr, and document that usage. Having both Display and
FromStr implementations where the result of Display cannot be parsed with FromStr may
surprise users.
§Examples
Basic implementation of FromStr on an example Point type:
use std::str::FromStr;
#[derive(Debug, PartialEq)]
struct Point {
x: i32,
y: i32
}
#[derive(Debug, PartialEq, Eq)]
struct ParsePointError;
impl FromStr for Point {
type Err = ParsePointError;
fn from_str(s: &str) -> Result<Self, Self::Err> {
let (x, y) = s
.strip_prefix('(')
.and_then(|s| s.strip_suffix(')'))
.and_then(|s| s.split_once(','))
.ok_or(ParsePointError)?;
let x_fromstr = x.parse::<i32>().map_err(|_| ParsePointError)?;
let y_fromstr = y.parse::<i32>().map_err(|_| ParsePointError)?;
Ok(Point { x: x_fromstr, y: y_fromstr })
}
}
let expected = Ok(Point { x: 1, y: 2 });
// Explicit call
assert_eq!(Point::from_str("(1,2)"), expected);
// Implicit calls, through parse
assert_eq!("(1,2)".parse(), expected);
assert_eq!("(1,2)".parse::<Point>(), expected);
// Invalid input string
assert!(Point::from_str("(1 2)").is_err());Required Associated Types§
Required Methods§
1.0.0 · Sourcefn from_str(s: &str) -> Result<Self, Self::Err>
fn from_str(s: &str) -> Result<Self, Self::Err>
Parses a string s to return a value of this type.
If parsing succeeds, return the value inside Ok, otherwise
when the string is ill-formatted return an error specific to the
inside Err. The error type is specific to the implementation of the trait.
§Examples
Basic usage with i32, a type that implements FromStr:
use std::str::FromStr;
let s = "5";
let x = i32::from_str(s).unwrap();
assert_eq!(5, x);Dyn Compatibility§
This trait is not dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.
Implementors§
Source§impl FromStr for ForwardKind
impl FromStr for ForwardKind
type Err = OpaqueError
§impl FromStr for ClientHint
impl FromStr for ClientHint
§impl FromStr for PerMessageDeflateIdentifier
impl FromStr for PerMessageDeflateIdentifier
type Err = Infallible
§impl FromStr for PseudoHeader
impl FromStr for PseudoHeader
type Err = InvalidPseudoHeaderStr
§impl FromStr for DirectoryServeMode
impl FromStr for DirectoryServeMode
type Err = OpaqueError
§impl FromStr for ElementPatchMode
impl FromStr for ElementPatchMode
type Err = Infallible
§impl FromStr for CrossOriginKind
impl FromStr for CrossOriginKind
type Err = Infallible
§impl FromStr for ReferrerPolicy
impl FromStr for ReferrerPolicy
type Err = Infallible
§impl FromStr for ApplicationProtocol
impl FromStr for ApplicationProtocol
type Err = Infallible
§impl FromStr for DeviceKind
impl FromStr for DeviceKind
type Err = OpaqueError
§impl FromStr for PlatformKind
impl FromStr for PlatformKind
type Err = OpaqueError
§impl FromStr for UserAgentKind
impl FromStr for UserAgentKind
type Err = OpaqueError
§impl FromStr for RequestInitiator
impl FromStr for RequestInitiator
type Err = OpaqueError
§impl FromStr for CidrSubnet
Obtains the CidrSubnet from the well-known
addr/prefix notation.
impl FromStr for CidrSubnet
Obtains the CidrSubnet from the well-known addr/prefix notation.
// The "192.0.2.0/24" example from
// https://tools.ietf.org/html/rfc5280#page-42
let subnet = CidrSubnet::from_str("192.0.2.0/24").unwrap();
assert_eq!(subnet, CidrSubnet::V4([0xC0, 0x00, 0x02, 0x00], [0xFF, 0xFF, 0xFF, 0x00]));1.0.0 · Source§impl FromStr for SocketAddr
impl FromStr for SocketAddr
type Err = AddrParseError
Source§impl FromStr for chrono::month::Month
Parsing a str into a Month uses the format %B.
impl FromStr for chrono::month::Month
Parsing a str into a Month uses the format %B.
§Example
use chrono::Month;
assert_eq!("January".parse::<Month>(), Ok(Month::January));
assert!("any day".parse::<Month>().is_err());The parsing is case-insensitive.
assert_eq!("fEbruARy".parse::<Month>(), Ok(Month::February));Only the shortest form (e.g. jan) and the longest form (e.g. january) is accepted.
assert!("septem".parse::<Month>().is_err());
assert!("Augustin".parse::<Month>().is_err());type Err = ParseMonthError
Source§impl FromStr for chrono::weekday::Weekday
Parsing a str into a Weekday uses the format %A.
impl FromStr for chrono::weekday::Weekday
Parsing a str into a Weekday uses the format %A.
§Example
use chrono::Weekday;
assert_eq!("Sunday".parse::<Weekday>(), Ok(Weekday::Sun));
assert!("any day".parse::<Weekday>().is_err());The parsing is case-insensitive.
assert_eq!("mON".parse::<Weekday>(), Ok(Weekday::Mon));Only the shortest form (e.g. sun) and the longest form (e.g. sunday) is accepted.
assert!("thurs".parse::<Weekday>().is_err());type Err = ParseWeekdayError
Source§impl FromStr for log::LevelFilter
impl FromStr for log::LevelFilter
type Err = ParseLevelError
§impl FromStr for PathAndQuery
impl FromStr for PathAndQuery
type Err = InvalidUri
§impl FromStr for LastEventId
impl FromStr for LastEventId
§impl FromStr for DnsResolveMode
impl FromStr for DnsResolveMode
type Err = OpaqueError
§impl FromStr for Http1HeaderName
impl FromStr for Http1HeaderName
type Err = InvalidHeaderName
§impl FromStr for HeaderName
impl FromStr for HeaderName
type Err = InvalidHeaderName
§impl FromStr for HeaderValue
impl FromStr for HeaderValue
type Err = InvalidHeaderValue
§impl FromStr for StatusCode
impl FromStr for StatusCode
type Err = InvalidStatusCode
§impl FromStr for DomainAddress
impl FromStr for DomainAddress
type Err = OpaqueError
§impl FromStr for ProxyAddress
impl FromStr for ProxyAddress
type Err = OpaqueError
§impl FromStr for SocketAddress
impl FromStr for SocketAddress
type Err = OpaqueError
§impl FromStr for ForwardedAuthority
impl FromStr for ForwardedAuthority
type Err = OpaqueError
§impl FromStr for ForwardedElement
impl FromStr for ForwardedElement
type Err = OpaqueError
§impl FromStr for ForwardedProtocol
impl FromStr for ForwardedProtocol
§impl FromStr for DeviceName
impl FromStr for DeviceName
type Err = OpaqueError
§impl FromStr for StringFilter
impl FromStr for StringFilter
type Err = Infallible
§impl FromStr for TraceState
impl FromStr for TraceState
§impl FromStr for rama::telemetry::tracing::level_filters::LevelFilter
impl FromStr for rama::telemetry::tracing::level_filters::LevelFilter
type Err = ParseLevelFilterError
§impl FromStr for NonEmptyString
impl FromStr for NonEmptyString
type Err = EmptyStringErr
Source§impl FromStr for ByteString
impl FromStr for ByteString
type Err = Infallible
1.5.0 · Source§impl FromStr for SocketAddrV4
impl FromStr for SocketAddrV4
type Err = AddrParseError
1.5.0 · Source§impl FromStr for SocketAddrV6
impl FromStr for SocketAddrV6
type Err = AddrParseError
Source§impl FromStr for DateTime<FixedOffset>
Accepts a relaxed form of RFC3339.
A space or a ‘T’ are accepted as the separator between the date and time
parts. Additional spaces are allowed between each component.
impl FromStr for DateTime<FixedOffset>
Accepts a relaxed form of RFC3339. A space or a ‘T’ are accepted as the separator between the date and time parts. Additional spaces are allowed between each component.
All of these examples are equivalent:
"2012-12-12T12:12:12Z".parse::<DateTime<FixedOffset>>()?;
"2012-12-12 12:12:12Z".parse::<DateTime<FixedOffset>>()?;
"2012- 12-12T12: 12:12Z".parse::<DateTime<FixedOffset>>()?;type Err = ParseError
Source§impl FromStr for DateTime<Local>
Accepts a relaxed form of RFC3339.
A space or a ‘T’ are accepted as the separator between the date and time
parts.
impl FromStr for DateTime<Local>
Accepts a relaxed form of RFC3339. A space or a ‘T’ are accepted as the separator between the date and time parts.
All of these examples are equivalent:
"2012-12-12T12:12:12Z".parse::<DateTime<Local>>()?;
"2012-12-12 12:12:12Z".parse::<DateTime<Local>>()?;
"2012-12-12 12:12:12+0000".parse::<DateTime<Local>>()?;
"2012-12-12 12:12:12+00:00".parse::<DateTime<Local>>()?;type Err = ParseError
Source§impl FromStr for DateTime<Utc>
Accepts a relaxed form of RFC3339.
A space or a ‘T’ are accepted as the separator between the date and time
parts.
impl FromStr for DateTime<Utc>
Accepts a relaxed form of RFC3339. A space or a ‘T’ are accepted as the separator between the date and time parts.
All of these examples are equivalent:
"2012-12-12T12:12:12Z".parse::<DateTime<Utc>>()?;
"2012-12-12 12:12:12Z".parse::<DateTime<Utc>>()?;
"2012-12-12 12:12:12+0000".parse::<DateTime<Utc>>()?;
"2012-12-12 12:12:12+00:00".parse::<DateTime<Utc>>()?;type Err = ParseError
Source§impl FromStr for NaiveDate
Parsing a str into a NaiveDate uses the same format,
%Y-%m-%d, as in Debug and Display.
impl FromStr for NaiveDate
Parsing a str into a NaiveDate uses the same format,
%Y-%m-%d, as in Debug and Display.
§Example
use chrono::NaiveDate;
let d = NaiveDate::from_ymd_opt(2015, 9, 18).unwrap();
assert_eq!("2015-09-18".parse::<NaiveDate>(), Ok(d));
let d = NaiveDate::from_ymd_opt(12345, 6, 7).unwrap();
assert_eq!("+12345-6-7".parse::<NaiveDate>(), Ok(d));
assert!("foo".parse::<NaiveDate>().is_err());type Err = ParseError
Source§impl FromStr for NaiveDateTime
Parsing a str into a NaiveDateTime uses the same format,
%Y-%m-%dT%H:%M:%S%.f, as in Debug.
impl FromStr for NaiveDateTime
Parsing a str into a NaiveDateTime uses the same format,
%Y-%m-%dT%H:%M:%S%.f, as in Debug.
§Example
use chrono::{NaiveDateTime, NaiveDate};
let dt = NaiveDate::from_ymd_opt(2015, 9, 18).unwrap().and_hms_opt(23, 56, 4).unwrap();
assert_eq!("2015-09-18T23:56:04".parse::<NaiveDateTime>(), Ok(dt));
let dt = NaiveDate::from_ymd_opt(12345, 6, 7).unwrap().and_hms_milli_opt(7, 59, 59, 1_500).unwrap(); // leap second
assert_eq!("+12345-6-7T7:59:60.5".parse::<NaiveDateTime>(), Ok(dt));
assert!("foo".parse::<NaiveDateTime>().is_err());type Err = ParseError
Source§impl FromStr for NaiveTime
Parsing a str into a NaiveTime uses the same format,
%H:%M:%S%.f, as in Debug and Display.
impl FromStr for NaiveTime
Parsing a str into a NaiveTime uses the same format,
%H:%M:%S%.f, as in Debug and Display.
§Example
use chrono::NaiveTime;
let t = NaiveTime::from_hms_opt(23, 56, 4).unwrap();
assert_eq!("23:56:04".parse::<NaiveTime>(), Ok(t));
let t = NaiveTime::from_hms_nano_opt(23, 56, 4, 12_345_678).unwrap();
assert_eq!("23:56:4.012345678".parse::<NaiveTime>(), Ok(t));
let t = NaiveTime::from_hms_nano_opt(23, 59, 59, 1_234_567_890).unwrap(); // leap second
assert_eq!("23:59:60.23456789".parse::<NaiveTime>(), Ok(t));
// Seconds are optional
let t = NaiveTime::from_hms_opt(23, 56, 0).unwrap();
assert_eq!("23:56".parse::<NaiveTime>(), Ok(t));
assert!("foo".parse::<NaiveTime>().is_err());type Err = ParseError
Source§impl FromStr for FixedOffset
Parsing a str into a FixedOffset uses the format %z.
impl FromStr for FixedOffset
Parsing a str into a FixedOffset uses the format %z.
type Err = ParseError
Source§impl FromStr for Url
Parse a string as an URL, without a base URL or encoding override.
impl FromStr for Url
Parse a string as an URL, without a base URL or encoding override.