$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote: julia> dump(Meta.parse(":(1+2)")) Expr head: Symbol quote args: Array{Any}((1 one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function

$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote: julia> dump(Meta.parse(":(1+2)")) Expr head: Symbol quote args: Array{Any}((1 one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function

$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote:CHAPTER 19. METAPROGRAMMING 252 julia> dump(Meta.parse(":(1+2)")) Expr one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function

$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote:CHAPTER 19. METAPROGRAMMING 252 julia> dump(Meta.parse(":(1+2)")) Expr one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function

$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote:CHAPTER 19. METAPROGRAMMING 252 julia> dump(Meta.parse(":(1+2)")) Expr one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function

$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote:CHAPTER 19. METAPROGRAMMING 252 julia> dump(Meta.parse(":(1+2)")) Expr one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function

$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote:CHAPTER 19. METAPROGRAMMING 252 julia> dump(Meta.parse(":(1+2)")) Expr one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function

$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote:CHAPTER 19. METAPROGRAMMING 249 julia> dump(Meta.parse(":(1+2)")) Expr one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function

$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote:CHAPTER 19. METAPROGRAMMING 249 julia> dump(Meta.parse(":(1+2)")) Expr one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function

$s do the equivalent of eval(eval(:x)). QuoteNode The usual representation of a quote form in an AST is an Expr with head :quote:CHAPTER 19. METAPROGRAMMING 249 julia> dump(Meta.parse(":(1+2)")) Expr one should keep in mind, that macro dispatch is based on the types of AST that are handed to the macro, not the types that the AST evaluates to at runtime: julia> macro m(::Int) println("An Integer") You annotate the function declaration with the @generated macro. This adds some information to the AST that lets the compiler know that this is a generated function. 2. In the body of the generated function