RIBA Academy will be hosting a webinar on Monday 16th November 2026 (12:00pm - 1:00pm). Webinar details: Learners will learn how to maxi...

Curated open-source guide to EU compliance (GPSR, CBAM, EUDR), sustainable materials sourcing, Incoterms risk transfer, and Hong Kong-based global supply chain architecture.

Moddable SDK 10.1 contains improvements made between October 17, 2026, and November 4, 2026. This is another big month for the Embedded JavaScript universe. Thank you to everyone who contributed. A...

As embodied carbon moves up the construction agenda, independently verified environmental data is changing how materials are assessed and specified. Capral Aluminium shares more. According to the Green Building Council of Australia, architects, engineers, builders and specifiers need data that quantifies the environmental impacts of construction products across a project or building’s lifecycle. These products include aluminium, steel, concrete, timber, insulation, and cladding. Environmental Product Declarations (EPDs) provide this information using a Life Cycle Assessment (LCA) carefully conducted against defined Product Category Rules (PCRs) and standards. An EPD is an independently verified document that reports quantified information about the environmental impacts of a product across defined stages of its lifecycle. Independent verification checks the LCA, underlying data, data handling and individual EPDs to confirm the information meets these requirements. As one of Australia’s largest aluminium suppliers and extruders for over 90 years, Capral Aluminium manufactures and supplies products for construction, transport and industrial sectors. To provide customers with transparent environmental data, Capral Aluminium is now independently verifying EPDs for its LocAl® and LocAl® SG lower-carbon aluminium extrusion ranges. The declarations provide lifecycle assessment data covering the cradle-to-gate environmental impacts of the products, from raw material supply through to manufacturing, known...

Domus Ventilation has expanded its thermal ducting offer with the introduction of a new all-in-one insulated ducting range, giving installers and specifiers greater choice when selecting the right duc...

Available as doors or doorsets, Dekordor SD and Visual Sensations present a new generation of products for a new generation of specifiers.

Mapping them to concepts from C# and the now-defunct C++/CX.

Learn the basics of Rust declarative macros! Understand the syntax, learn the terminology, demystify macro hygiene, and explore fragment specifiers.

One place that specifiers do better is by affecting nested values as well. If I want to print the first 3 items of a matrix, I'm stuck with all of the elements of each orthogonal item for those 3 items.

I think special format specifiers would be bad design, because that information is passed to _every_ type, but it doesn't make sense for all types. Adapters are the way to go. For the same reason, I think the current design is broken: the format specifiers already don't apply to all types. This compiles but is wrong: println!("{:#.7}", "abc"); It would have been better if all the custom formatting options were done by adapters: println!("{}", PI.display().scientific().precision(7)); // Compile error: no method `precision`. println!("{}", "abc".display().precision(7));

I think adapters here seem like the way to go. The biggest reason those are less good is that derives don't naturally use them, but derives don't naturally use a new max-length specifier either, so this solution doesn't avoid that limitation. Adding more stuff into format specifiers is pretty high impact.

Learn the basics of Rust declarative macros! Understand the syntax, learn the terminology, explore macro hygiene, and master fragment specifiers.