[ https://issues.apache.org/jira/browse/MESOS-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610980#comment-14610980 ]
Benjamin Mahler commented on MESOS-2965: ---------------------------------------- It seems simpler to have either, or both of: (1) Implicit casting from Path to string, (2) Implicit construction of Path from string? Otherwise, we're likely to end up with a lot of overloads and conversions in calling code. > Stout os functions don't take Path > ----------------------------------- > > Key: MESOS-2965 > URL: https://issues.apache.org/jira/browse/MESOS-2965 > Project: Mesos > Issue Type: Improvement > Components: stout > Reporter: Artem Harutyunyan > Priority: Minor > Labels: beginner, mesosphere, newbie, stout > > For example: > {code}inline Try<Nothing> rm(const std::string& path){code} does not have an > overload for {code}inline Try<Nothing> rm(const Path& path){code} > The implementation should be something like: > {code} > inline Try<Nothing> rm(const Path& path) > { > rm(path.value); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)