[llvm-dev] [libcxx] Unimplemented path functions inquiry
Chris Tetreault via llvm-dev
llvm-dev at lists.llvm.org
Thu Oct 14 09:18:36 PDT 2021
I don’t know of any plans to implement this functionality, but I agree that the least we can do is provide a function body that asserts or calls something like report_fatal_error.
From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Muiez Ahmed via llvm-dev
Sent: Wednesday, October 13, 2021 1:33 PM
To: llvm-dev at lists.llvm.org
Subject: [llvm-dev] [libcxx] Unimplemented path functions inquiry
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
I hope this email finds you well. I have an inquiry about the following unimplemented functions declared in `libcxx/include/filesystem`:
// TODO Implement locale conversions.
class = _EnableIfPathable<_Source,
path(const _Source& __src,
const locale& __loc, format = format::auto_format);
path(_InputIt __first, _InputIt _last,
const locale& __loc,
format = format::auto_format);
In particular, there is a TODO (introduced in the following commit 998a5c88312066fcc2b2de1358edc76587611354) that says "Implement locale conversions". Since these functions are not implemented, they are causing a link time error on z/OS. Hence, is there a plan to implement them? Or is there a way to cause compiler time errors if those functions are used? If not, should we leave it as is or provide a definition that asserts (to be more user friendly)?.
E-mail: muiez at ibm.com<mailto:muiez at ibm.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev