See rust-lang/rust#63252 and rust-lang/rfcs#1954.

The official recommendation about cloning reference counted pointers should be added to the style guide since it is being pulled from the standard library documentation

Reporting an issue

Thank you for taking an interest in rrule! Please include the following in
your report:

• Verify that you've looked through existing issues for duplicates before
  creating a new one
• Code sample reproducing the issue. Be sure to include all input values you
  are using such as the exact RRule string and dates.
• Expected output
• Actual output

Currently, react-native-windows needs to create an overridden metro.config.js due to the windows platform having a bunch of platform overrides. This makes it difficult for customers to target multiple platforms.... Once re

I'm looking for a convention/standard to document components, especially targeting these information:

• arguments
• attributes
• yield

for components, template-only components while supporting for java- and typescript. Primarily focused for glimmer components, yet the js-only approach should also be suitable to be applied to ember components, too.

The idea is, that these conventions can

The Extension Registry is just a stub.

Two things must be done asap:

• add existing extensions
• define how to register extensions

Currently 301 redirects are not cached at all unless the website returns a satisfying cache-control header. This is not how browsers work.

https://stackoverflow.com/questions/9130422/how-long-do-browsers-cache-http-301s

There should be a setting to cache 301 redirects for an arbitrary default time.

Both caching and semantics make some references to h1-messaging. They should not be normative.

We can do this by:

• Removing unnecessary references
• Turning references into examples / advisory text
• Clarifying H1 specificity where appropriate

Includes #332, #333, #311, #259, #183, #182, #118.

See today's thread on gen-art about this.

The answer to:

Why aren't per-directory well-known locations defined?

Given in Appendix A could be moved into Section 3.

  Allowing every URI path segment to have a well-known location
  (e.g., "/images/.well-known/") would increase the risks of

https://github.com/martinthomson/i-d-template/blob/master/v3.css selects the "Cabin Condensed" font for section titles. I find the narrow letters hard to read and would prefer a normal width font instead.

The current version of the RFC has an example that contains the following:

  "notes": [""],
  "output": "",

In general, empty strings and arrays are omitted (treated the same as nil/null), so it would probably be better to add example values to these items.