internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello end bad_read2(a) # it is NOT safe to access `a` here Using locks to avoid data-races An important tool to avoid data-races, and thereby write thread-safe code, is the concept of a "lock". A lock can be

internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello end bad_read2(a) # it is NOT safe to access `a` here Using locks to avoid data-races An important tool to avoid data-races, and thereby write thread-safe code, is the concept of a "lock". A lock can be

internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello end bad_read2(a) # it is NOT safe to access `a` here Using locks to avoid data-races An important tool to avoid data-races, and thereby write thread-safe code, is the concept of a "lock". A lock can be

internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello end bad_read2(a) # it is NOT safe to access `a` here Using locks to avoid data-races An important tool to avoid data-races, and thereby write thread-safe code, is the concept of a "lock". A lock can be

internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello end bad_read2(a) # it is NOT safe to access `a` here Using locks to avoid data-races An important tool to avoid data-races, and thereby write thread-safe code, is the concept of a "lock". A lock can be

internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello end bad_read2(a) # it is NOT safe to access `a` here Using locks to avoid data-races An important tool to avoid data-races, and thereby write thread-safe code, is the concept of a "lock". A lock can be

internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello end bad_read2(a) # it is NOT safe to access `a` here Using locks to avoid data-races An important tool to avoid data-races, and thereby write thread-safe code, is the concept of a "lock". A lock can be

internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello end bad_read2(a) # it is NOT safe to access `a` here Using locks to avoid data-races An important tool to avoid data-races, and thereby write thread-safe code, is the concept of a "lock". A lock can be

internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello declare an isbits struct type and use that instead. Unnamed structs are not possible in the translation to Julia. Packed structs and union declarations are not supported by Julia.CHAPTER 27. CALLING

internals of a program and its types just like any other data. Warning Metaprogramming is a powerful tool, but it introduces complexity that can make code more difficult to understand. For example, it can quoted return expression using the function macroexpand (important note: this is an extremely useful tool for debugging macros): julia> ex = macroexpand(Main, :(@sayhello("human")) ) :(Main.println("Hello declare an isbits struct type and use that instead. Unnamed structs are not possible in the translation to Julia. Packed structs and union declarations are not supported by Julia.CHAPTER 27. CALLING