Async and Thread Safety
SmartFormat makes heavy use of caching and object pooling for expensive operations, which both require static containers.
SmartFormatters and Parsers require one instance per thread.
When instantiating SmartFormatters from different threads, SmartSettings.IsThreadSafeMode=true must be set, so that thread-safe containers are used. This brings an inherent performance penalty.
Note: The simplified Smart.Format(...) API overloads use a static SmartFormatter instance which is not thread-safe. Call Smart.CreateDefaultSmartFormat() to create a SmartFormatter with defaults.
When instantiating SmartFormatters from a single thread, SmartSettings.IsThreadSafeMode=false should be set for avoiding the multithreading overhead and thus for best performance. This is the default.
The static Smart.Format(...) API overloads are allowed here.
3.3- Syntax, Terminology
- Placeholders and Nesting
- string.Format Compatibility
- Character Literals in Format Strings
- HTML With CSS or JavaScript
- Data Source Extensions
- Default _ DefaultFormatter
- Lists _ ListFormatter
- Choose _ ChooseFormatter
- Condition _ ConditionalFormatter
- Null _ NullFormatter
- SubString _ SubStringFormatter
- RegEx _ IsMatchFormatter
- Pluralization _ PluralLocalizationFormatter
- Localization _ LocalizationFormatter
- Templates _ TemplateFormatter
- TimeSpan _ TimeFormatter
- XML _ XElementFormatter
- Extension Methods
- Home
- Common Pitfalls
- HTML with CSS or JavaScript
- Overview
- Main Features
- Formatters
- Extra Features
- Console and StringBuilder
- TemplateFormatter
- SmartSettings to control Smart.Format behavior
- Additional Info
- License