Diagnostic dynamic argument

crates/parser/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "as3_parser"
-version = "0.5.25"
+version = "0.5.26"
 edition = "2021"
 authors = ["hydroper <[email protected]>"]
 repository = "https://github.com/hydroper/as3parser"

crates/parser/diagnostics/diagnostics.rs

@@ -162,6 +162,7 @@ impl Diagnostic {
         match argument {
             DiagnosticArgument::String(s) => s.clone(),
             DiagnosticArgument::Token(t) => t.to_string(),
+            DiagnosticArgument::Dynamic(d) => d.to_string(),
         }
     }
 }
@@ -174,4 +175,9 @@ pub macro diagnostic_arguments {
 pub enum DiagnosticArgument {
     String(String),
     Token(Token),
+    Dynamic(Rc<dyn DynamicDiagnosticArgument>),
+}
+
+pub trait DynamicDiagnosticArgument {
+    fn to_string(&self) -> String;
 }

docs/diagnostics.md

@@ -63,6 +63,4 @@ If you want, for simple debugging purposes, you may finish formatting your own m
 diagnostic.format_with_message("My message", Some(custom_id_number))
 ```
 
-For real use cases, calling `.format_with_message()` is not preferred if your application is not solely in English, since it will add categories such as `Warning`.
-
-Moreover, argument variants in `as3_parser::ns::Diagnostic` may not be enough. For example, a compiler may want to store a symbol argument; in this case, an extra layer over `as3_parser::ns::Diagnostic` must be provided, supporting more variants.
+For real use cases, calling `.format_with_message()` is not preferred if your application is not solely in English, since it will add categories such as `Warning`.