[orc-rt] Add SPSSequence serialization from iterator_range. (#207715)
Adds an SPSSerializationTraits specialization that serializes an
iterator_range<IteratorT> as an SPSSequence<SPSElementTagT>, matching
the wire format of the existing container and span sequence serializers.
The element type is deduced via std::iterator_traits, so both class-type
iterators and raw pointers are supported.
This lets callers serialize an arbitrary [begin, end) sub-range
directly, without first copying the elements into a temporary container.
Only serialization is provided: a bare iterator pair has no meaningful
deserialization target, so decode into a std::vector (or other sequence
type) as usual.
Please enter the commit message for your changes. Lines starting
libdoom-umapinfo: Update to 1.1.0
1.1.0 2026-07-03 Release
--------------------------
Important notes:
- Add REUSE information
Package is REUSE 3.3 conformant (according to "reuse lint")
- HTML documentation is no longer included in the distribution.
It can be viewed online
Bug fixes:
- Add copyright and licence declarations for UMAPINFO specification
(parts are used in examples for CLI utility, but not installed)
- Add copyright and licence declarations for "2022 A Doom Odyssey"
(UMAPINFO lump is used for testsuite and in examples for CLI utility,
but not installed)
New features and improvements:
[11 lines not shown]
yq: updated to 4.1.1
Changes for v4.1.1 (2026-07-03)
- xq: support –xml-short-empty-elements to emit self-closing elements
instead of the long form
Changes for v4.1.0 (2026-07-03)
- Implement YAML comment roundtripping
Changes for v4.0.0 (2026-07-02)
- Implement TOML comment roundtripping (tomlq -T)
- Add –width=0 for no-wrap option; –null-input as -n alias
- Force quote strings that can be parsed as integers in YAML 1.2
- Implement YAML 1.2 octals
- Prevent exception thrown when sys.stdin is None.
libc/resolv: Add no-debug and no-rotate options
These are simply the reverse of the debug and rotate options.
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D57926
libc/resolv: Reimplement the sortlist parser
When we switched from the BIND4 resolver to the BIND9 resolver, the
sortlist parser was inadvertently disabled due to a missing #define, and
nobody seemed to notice. The sorting code remained enabled in the
resolver, but there was no way to set a sort order.
Reimplement the sortlist parser, but correctly, and update the manual
accordingly. The new parser accepts IPv4 and IPv6 addresses with or
without a mask or prefix length, just like the old one, except IPv6
support was a bit wonky in the original code.
Fixes: 5342d17f09a8 ("Update the resolver in libc to BIND9's one.")
Relnotes: yes
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D57925
libc/resolv: Refactor the configuration parser
This was previously all a single loop in res_init(), apart from option
parsing which we cleaned up in a previous commit. Break it out into
separate functions for reading the configuration line by line, setting
the default domain, setting the search list, and adding a nameserver
to the nameserver list. Sprinkle bounds checks and code comments all
around.
The sortlist code, which has been disabled for the past 20 years, will
be dealt with in a separate commit.
MFC after: 1 week
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D57924
libc/resolv: Refactor the option parser
Start the loop by finding the end of the option name, the name-value
separator (if any), and the end of the option. Use those pointers to
simplify matching the option name and parsing the option value, and
validate option names and values more strictly. This means that:
* We no longer accept trailing garbage in an option name or value. For
instance, we would previously interpret “edns0123” as “edns0” and
“timeout:3xyz” as “timeout:3”. This was actually quite lucky because
we also failed to recognize the newline at the end of the option line
as a whitespace character.
* For options that take a numerical argument, we would previously accept
negative values and treat non-numerical arguments as 0, while large
numerical arguments would be capped to the option's maximum permitted
value. Now, any failure to parse the argument, including overflow,
results in the option being left unchanged.
[4 lines not shown]
resolver(5): Overhaul
* Modernize the markup
* Describe the comment syntax
* Drop obsolete advice
* Capitalize sentences
* Improve the language
* Replace no_tld_query with no-tld-query; both are supported, but all the
other multi-word options use hyphens rather than underscores.
* Add missing ENVIRONMENT section
* Redo the example
[3 lines not shown]
