#AREA OF CIRCLE USING MACRO IN C FULL#

Mostly because even templates have structure and checks to them. I kind of want both systems to exist in one language. Yes, what you will, completely unprincipled trial-and-error specialization based on 'did the emitted text compile?' does let you express some absolutely jacked up stuff that parametric systems balk this might be blasphemy, but. Wait, why are we introducing template errors into Rust? Aren't parametric generics (like Rust traits) which provide pre-monomorphization checks and prevent (most) post-monomorohization errors better? Didn't C++20 add concepts specifically to enable moving some template type checking forward? This allows Rust to express the benefit of C++-style duck-typed function templates where macro_rules! might otherwise be used while still providing a developer experience better than using C++ templates or Rust macro_rules! for the same task. A few sections have todos left to mark where I think detail is probably missing please feel free to ask clarifying questions even/especially if they ask about the todo areas, as I'm just marking them as likely needing more clarification, not trying to defer the clarification.) SummaryĪdd a new type of item, macro fn, which is defined and used almost exactly like a function but which allows deferring name resolution and type checking to instantiation-time like a macro.

This was written in one afternoon/evening on my smartphone please forgive any formatting/grammar/procedural issues.

#AREA OF CIRCLE USING MACRO IN C FULL#

(I unfortunately don't have the bandwidth to actually put this through a full RFC for language inclusion, but this is a legitimate Request For Comments and proposal for improving the capability of Rust.

Area of circle using macro in c