[libcxx-commits] [libcxx] [libc++] Add FreeBSD-specific EINTEGRITY errc value (PR #76364)

[Dimitry Andric via libcxx-commits]

DimitryAndric wrote:

Hm, it looks like clang-format went completely crazy due to my latest change. For some reason it now wants to reformat the enum as:

```c++
_LIBCPP_DECLARE_STRONG_ENUM(errc) {
  address_family_not_supported = EAFNOSUPPORT, address_in_use = EADDRINUSE, address_not_available = EADDRNOTAVAIL,
  already_connected = EISCONN, argument_list_too_long = E2BIG, argument_out_of_domain = EDOM, bad_address = EFAULT,
  bad_file_descriptor = EBADF, bad_message = EBADMSG, broken_pipe = EPIPE, connection_aborted = ECONNABORTED,
  connection_already_in_progress = EALREADY, connection_refused = ECONNREFUSED, connection_reset = ECONNRESET,
  cross_device_link = EXDEV, destination_address_required = EDESTADDRREQ, device_or_resource_busy = EBUSY,
  directory_not_empty = ENOTEMPTY, executable_format_error = ENOEXEC, file_exists = EEXIST, file_too_large = EFBIG,
  filename_too_long = ENAMETOOLONG, function_not_supported = ENOSYS, host_unreachable = EHOSTUNREACH,
  identifier_removed = EIDRM, illegal_byte_sequence = EILSEQ, inappropriate_io_control_operation = ENOTTY,
#if defined(__FreeBSD__) && defined(EINTEGRITY) // FreeBSD extension
...
```

Does anybody understand clang-format sufficiently to know what I have to do to avoid this weirdness? :)

https://github.com/llvm/llvm-project/pull/76364