# Built-in Macro object

**URL:** <https://es.discourse.group/t/built-in-macro-object/922>\
**Category:** 💡 Ideas\
**Created:** [August 13, 2021, 7:56am UTC](https://es.discourse.group/t/built-in-macro-object/922 "2021-08-13T07:56:24Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![alshdavid](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/alshdavid/32/915_2.png) [@alshdavid](https://es.discourse.group/u/alshdavid)\
**Post date:** [October 25, 2025, 1:13am UTC](https://es.discourse.group/t/built-in-macro-object/922/10 "2025-10-25T01:13:04Z")

</div>

EDIT: Sorry for reviving an old thread. I just saw it in the related threads and thought to reference the other post before seeing the dates 😅

Related. I raised an idea proposing inline and procedural macros inspired by Rust's macro system.

Defining macros would be done such that they can be evaluated at runtime or compiled statically by compilers (like `swc`) and using an adapted ES-idiomatic syntax based on the existing Rust macro definition syntax.

> [@Inline Macros](https://es.discourse.group/t/inline-macros/2455):
>
> Disclaimer: No AI was used in the making of this post What are Macros? Note: the syntax semantics are only an example for demonstration Macros are a pre-processing step that allows developers to use templating-like syntax to describe code generation. For example, an inline macro: let result = add!(1, 1); Prior to evaluation, would expand into: let result = 2; Why is this needed? The Current Landscape Almost every single non-trivial JavaScript and TypeScript application already uses "macro…

---

_[View the full topic](https://es.discourse.group/t/built-in-macro-object/922)._