Files
tubestation/third_party/rust/ron/docs/extensions.md
Erich Gubler 6f3b669604 Bug 1956123 - build(webgpu): update WGPU to c7c79a0dc9356081a884b5518d1c08ce7a09c7c5 r=webgpu-reviewers,supply-chain-reviewers,nical
Notable WebGPU CTS changes:

- Demotions from tier 2 to tier 3:
	- `webgpu:shader,execution,expression,unary,{i32,u32}_conversion:f32:*` started regressing on Windows.
- Promotions to tier 2 from tier 3:
	- Across all platforms:
		- `webgpu:shader,execution,expression,call,builtin,cross:f32:*`
		- `webgpu:shader,execution,expression,unary,i32_conversion:abstract_float:*`
		- `webgpu:shader,execution,expression,unary,u32_conversion:abstract_float:*`
		- `webgpu:shader,execution,limits:nesting_depth_braces:*`
		- `webgpu:shader,validation,expression,call,builtin,value_constructor:vector_copy:*`
		- `webgpu:shader,validation,expression,call,builtin,value_constructor:vector_elementwise:*`
		- `webgpu:shader,validation,expression,call,builtin,value_constructor:vector_mixed:*`
	- `webgpu:shader,validation,expression,call,builtin,value_constructor:scalar_zero_value:*` was promoted on Linux and Windows, but stays in macOS on account of failing `f16` functionality. My guess is that these failures are also present on the other platforms, but we don't see the because `shader-f16` is not aviailable on our other CI platforms yet.
	- From macOS, completing the set of all platforms passing:
		- `f16` functionality, which, again, was likely not visible on our other CI platforms before:
			- `webgpu:shader,execution,expression,call,builtin,cross:f16:*`
			- `webgpu:shader,validation,decl,override:type:*`
	- `webgpu:api,validation,capability_checks,limits,maxUniformBufferBindingSize:createBindGroup,at_over:*`
	  was promoted on Windows.

Differential Revision: https://phabricator.services.mozilla.com/D243593
2025-04-02 00:36:43 +00:00

3.9 KiB

RON extensions

RON has extensions that can be enabled by adding the following attribute at the top of your RON document:

#![enable(...)]

unwrap_newtypes

You can add this extension by adding the following attribute at the top of your RON document:

#![enable(unwrap_newtypes)]

This feature enables RON to automatically unwrap simple tuples.

struct NewType(u32);
struct Object {
    pub new_type: NewType,
}

Without unwrap_newtypes, because the value 5 can not be saved into NewType(u32), your RON document would look like this:

(
    new_type: (5),
)

With the unwrap_newtypes extension, this coercion is done automatically. So 5 will be interpreted as (5).

#![enable(unwrap_newtypes)]
(
    new_type: 5,
)

implicit_some

You can add this extension by adding the following attribute at the top of your RON document:

#![enable(implicit_some)]

This feature enables RON to automatically convert any value to Some(value) if the deserialized type requires it.

struct Object {
    pub value: Option<u32>,
}

Without this feature, you would have to write this RON document.

(
    value: Some(5),
)

Enabling the feature would automatically infer Some(x) if x is given. In this case, RON automatically casts this 5 into a Some(5).

(
    value: 5,
)

With this extension enabled, explicitly given None and Some(..) will be matched eagerly on Option<Option<Option<u32>>>, i.e.

  • 5 -> Some(Some(Some(5)))
  • None -> None
  • Some(5) -> Some(Some(Some(5)))
  • Some(None) -> Some(None)
  • Some(Some(5)) -> Some(Some(Some(5)))
  • Some(Some(None)) -> Some(Some(None))
  • Some(Some(Some(5))) -> Some(Some(Some(5)))

unwrap_variant_newtypes

You can add this extension by adding the following attribute at the top of your RON document:

#![enable(unwrap_variant_newtypes)]

This feature enables RON to automatically unwrap newtype enum variants.

#[derive(Deserialize)]
struct Inner {
    pub a: u8,
    pub b: bool,
}
#[derive(Deserialize)]
pub enum Enum {
    A(Inner),
    B,
}

Without unwrap_variant_newtypes, your RON document would look like this:

(
    variant: A(Inner(a: 4, b: true)),
)

With the unwrap_variant_newtypes extension, the first structural layer inside a newtype variant will be unwrapped automatically:

#![enable(unwrap_newtypes)]
(
    variant: A(a: 4, b: true),
)

Note that when the unwrap_variant_newtypes extension is enabled, the first layer inside a newtype variant will always be unwrapped, i.e. it is no longer possible to write A(Inner(a: 4, b: true)) or A((a: 4, b: true)).

explicit_struct_names

During serialization, this extension emits struct names. For instance, this would be emitted:

Foo(
    bar: Bar(42),
)

During deserialization, this extension requires that all structs have names attached to them. For example, the following deserializes perfectly fine:

Foo(
    bar: Bar(42),
)

However, with the explicit_struct_names extension enabled, the following will throw an ExpectedStructName error:

(
    bar: Bar(42),
)

Similarly, the following will throw the same error:

Foo(
    bar: (42),
)

Note that if what you are parsing is spread across many files, you would likely use Options::with_default_extension to enable Extensions::EXPLICIT_STRUCT_NAMES before the parsing stage. This is because prepending #![enable(explicit_struct_names)] to the contents of every file you parse would violate DRY (Don't Repeat Yourself).

Here is an example of how to enable explicit_struct_names using this method:

use ron::extensions::Extensions;
use ron::options::Options;

// Setup the options
let options = Options::default().with_default_extension(Extensions::EXPLICIT_STRUCT_NAMES);
// Retrieve the contents of the file
let file_contents: &str = /* ... */;
// Parse the file's contents
let foo: Foo = options.from_str(file_contents)?;