MCQs on Macros and Metaprogramming | Scala
Dive deep into macros, metaprogramming, runtime reflection, and Scala Meta utilities with these 30 essential MCQs. Enhance your understanding of Scala’s advanced capabilities for code generation and type manipulation.
Macros and Metaprogramming in Scala
1. Macros in Scala
- What is the primary purpose of macros in Scala?
- A) To optimize runtime performance
- B) To generate code at compile-time
- C) To improve logging features
- D) To enhance debugging
- What is the key advantage of compile-time macros in Scala?
- A) Faster execution at runtime
- B) Automatic serialization of data
- C) Type-safe code generation
- D) Better thread safety
- Which keyword is used to define a macro in Scala?
- A)
macro - B)
def - C)
compile - D)
reflect
- A)
- What does a macro return during compilation?
- A) A runtime value
- B) Abstract syntax trees (ASTs)
- C) Serialized data
- D) A runtime error
- In which phase of compilation do macros execute?
- A) Parsing phase
- B) Semantic analysis phase
- C) Code generation phase
- D) Type-checking phase
- Which of the following is a limitation of macros in Scala?
- A) They cannot access runtime data
- B) They are not type-safe
- C) They reduce runtime performance
- D) They can only be used with primitive types
- Which API is commonly used for macro implementation in Scala 2?
- A)
scala.reflect.macros.blackbox.Context - B)
scala.meta.macros - C)
java.lang.reflect - D)
scalaz.macros
- A)
- What is one of the primary goals of macros in functional programming?
- A) To improve runtime type checking
- B) To eliminate boilerplate code
- C) To enforce immutability
- D) To handle concurrency
- What feature replaced macros in Scala 3?
- A) Inline methods and quotes
- B) Reflection API
- C) Abstract type members
- D) Higher-order functions
- Why are macros considered experimental in Scala 2?
- A) They are not officially supported by the Scala compiler
- B) They have unpredictable runtime behavior
- C) They lack a stable API
- D) They require external libraries
2. Reflection and Runtime Type Information
- What is runtime reflection in Scala used for?
- A) To manipulate the AST
- B) To inspect and modify program structure at runtime
- C) To enhance type inference
- D) To serialize objects
- Which Scala package provides reflection capabilities?
- A)
scala.runtime - B)
scala.reflect - C)
scala.meta.reflect - D)
scala.util.reflect
- A)
- What is a
TypeTagin Scala?- A) A runtime representation of a type
- B) A macro for code generation
- C) A trait for higher-kinded types
- D) An annotation for type aliases
- What is a
Manifestin Scala?- A) A deprecated way to access type information
- B) A compile-time annotation
- C) A runtime container for ASTs
- D) A functional programming construct
- Which of the following can be used to inspect method details at runtime?
- A)
Classobjects in Java Reflection - B)
scala.reflect.runtime.universe - C)
TypeTagandManifest - D) All of the above
- A)
- Why is runtime reflection less favored in functional programming?
- A) It breaks immutability principles
- B) It introduces runtime overhead
- C) It lacks type safety
- D) All of the above
- What is the
ToolBoxin Scala Reflection API?- A) A utility to execute Scala code at runtime
- B) A container for runtime types
- C) A debugger for macros
- D) A logger for errors
- How does
TypeTagdiffer fromClassTag?- A)
TypeTagprovides full type information, whileClassTagfocuses on erased types - B)
ClassTagis used for runtime reflection only - C)
TypeTagcannot access generic types - D)
ClassTagis faster but less precise
- A)
- What is one drawback of using runtime reflection in Scala?
- A) Reduced runtime performance
- B) Loss of type safety
- C) Increased code complexity
- D) All of the above
- Which method allows dynamic code evaluation using Scala Reflection?
- A)
ToolBox.eval - B)
Manifest.invoke - C)
TypeTag.execute - D)
Reflect.run
- A)
3. Scala Meta and its Utilities
- What is the primary use of Scala Meta?
- A) Runtime code manipulation
- B) Compile-time code analysis and transformation
- C) Thread management
- D) Parallel computation
- Which library supports the creation of custom linting tools in Scala?
- A) Scala Meta
- B) Cats Effect
- C) ZIO
- D) Play Framework
- What are quasiquotes in Scala Meta?
- A) A way to construct and deconstruct syntax trees
- B) A debugging utility
- C) A runtime optimization tool
- D) A type aliasing mechanism
- What is a
Treein Scala Meta?- A) A representation of Scala code
- B) A mutable data structure
- C) A macro container
- D) A runtime exception
- What replaced Scala Macros for most use cases in Scala 3?
- A) Scala Meta
- B) Inline and quotes
- C) Futures
- D) Higher-order functions
- Which tool in Scala Meta is used for parsing Scala code?
- A)
Tree - B)
Parser - C)
ToolBox - D)
MacroUtils
- A)
- What is a
SemanticDBin Scala Meta?- A) A database for storing semantic information about Scala code
- B) A concurrency tool
- C) A runtime debugger
- D) A type-safe serialization library
- Which component of Scala Meta is used for code analysis?
- A)
ScalametaParser - B)
SemanticDB - C)
ToolBox - D)
AST
- A)
- What is the primary goal of Scala Meta in tool development?
- A) To enable advanced type inference
- B) To simplify the creation of compilers and code analysis tools
- C) To handle runtime reflection
- D) To provide support for monads
- What is a common application of Scala Meta utilities?
- A) Building IDE plugins
- B) Creating code formatters
- C) Developing static code analyzers
- D) All of the above
Answer Key
| Qno | Answer (Option with the text) |
|---|---|
| 1 | B) To generate code at compile-time |
| 2 | C) Type-safe code generation |
| 3 | A) macro |
| 4 | B) Abstract syntax trees (ASTs) |
| 5 | B) Semantic analysis phase |
| 6 | A) They cannot access runtime data |
| 7 | A) scala.reflect.macros.blackbox.Context |
| 8 | B) To eliminate boilerplate code |
| 9 | A) Inline methods and quotes |
| 10 | C) They lack a stable API |
| 11 | B) To inspect and modify program structure at runtime |
| 12 | B) scala.reflect |
| 13 | A) A runtime representation of a type |
| 14 | A) A deprecated way to access type information |
| 15 | D) All of the above |
| 16 | D) All of the above |
| 17 | A) A utility to execute Scala code at runtime |
| 18 | A) TypeTag provides full type information, while ClassTag focuses on erased types |
| 19 | D) All of the above |
| 20 | A) ToolBox.eval |
| 21 | B) Compile-time code analysis and transformation |
| 22 | A) Scala Meta |
| 23 | A) A way to construct and deconstruct syntax trees |
| 24 | A) A representation of Scala code |
| 25 | B) Inline and quotes |
| 26 | B) Parser |
| 27 | A) A database for storing semantic information about Scala code |
| 28 | B) SemanticDB |
| 29 | B) To simplify the creation of compilers and code analysis tools |
| 30 | D) All of the above |