# class Published articles for class. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Magic statics vs. std::call\_once DevFeed: [Magic statics vs. std::call\_once]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-16T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [Code](), [Caching](), [execution](), [function](), [class]() Tags: [cache](), [class](), [code](), [execution](), [function](), [old-new-thing](), [static]() ### AI overview The article compares function-local static variables with std::call_once for caching values that are expensive to calculate. It explains why magic statics are unsuitable for lazily initializing per-instance data and points to deferred execution as a related alternative. ### Source excerpt They sort of do the same thing, but differently. The post Magic statics vs. std::call_once appeared first on The Old New Thing. ## Code Smell 321 - Getter Piggybacking DevFeed: [Code Smell 321 - Getter Piggybacking]() Original publisher: [Read original article]() Author: Maxi Contieri Published: 2026-08-20T02:51:49Z Content type: article Language: en Sources: [Maximiliano Contieri - Software Design]() Topics: [Refactoring](), [Code]() Tags: [business-logic](), [class](), [code](), [refactoring]() ### AI overview This article explains a code smell in which an existing getter is reused to implement business logic outside the object that owns the value. It describes the resulting duplicated rules, broken encapsulation, scattered comparisons, and fragile refactoring, and recommends adding behavior methods, keeping comparisons inside the object, passing collaborators instead of primitives, and using getters mainly for rendering. ### Source excerpt TL;DR: Don't reuse an existing getter to bolt on new business logic from outside the object. Problems 😔 Duplicated business rules Broken encapsulation Scattered comparison logic Hidden domain kn ## Weekly Update 517: Cyber Ransoms DevFeed: [Weekly Update 517: Cyber Ransoms]() Original publisher: [Read original article]() Author: Troy Hunt Published: 2026-08-18T03:44:58Z Content type: opinion Language: en Sources: [Troy Hunt]() Topics: [ransomware](), [Cybercrime]() Tags: [breach](), [class](), [cyber](), [ransomware](), [weekly-update]() ### AI overview The article comments on ransomware as extortion, the financial motives of attackers, and the legal and communication pressures faced by breached companies. ### Source excerpt The current ransomware situation is a bit of a kludge (deep breath): a lot of ransomware (which often doesn't even involve "ware", it's just extortion) is carried out by kids who successfully make a truckload of money but can't spend it without ## Why Two Similar Compiler Cases Cannot Share One Calling Convention DevFeed: [Why Two Similar Compiler Cases Cannot Share One Calling Convention]() Original publisher: [Read original article]() Author: Brendan Sechter Published: 2026-08-07T09:00:00Z Content type: article Language: en Sources: [Brendan A R Sechter's Development Blog]() Topics: [Compiler](), [interface](), [Back end](), [test](), [Mathematics]() Tags: [article](), [backend](), [case-study](), [class](), [compiler](), [compilers](), [engineering](), [interface](), [mathematics](), [measurement](), [verification]() ### AI overview This compiler backend case study argues that two similar cases cannot be unified when one must report two values through an interface with only one available slot. A counting argument shows that the apparent similarity of nine measured occurrences is irrelevant to the shared interface design. The article also identifies an earlier rule that unnecessarily excluded ten of twenty-four cases. ### Source excerpt A system had grown two ways of doing what looked like one thing. The obvious move was to tidy them into one. The tidying turns out to be impossible, and the reason it is impossible is the reason the two ways exist. The argument that settles it needs no specialist knowledge and fits in a sentence. One of the two cases has two things to report and only one slot to report them in. Whichever thing the slot is given, the other is lost. The other case has only one thing to report, so the single slot is exactly enough. That is a counting argument, it is decided before any code is written, and it is not the argument an engineer reaches for by default. The engineer's instinct is to look at the cases and ask whether they resemble one another. They did. Every one of the nine measured occurrences had exactly the shape that invited the tidy-up, and the measurement encouraged precisely the wrong conclusion. The resemblance was real and it was irrelevant, because the defect was never in the instances. It was in the interface they would have had to share. This article is about that distinction, which is between evidence about members of a class and evidence about the channel the class must pass through. The second dominates the first and is cheaper to check. The article reports the measurement, the way the measurement pointed the wrong direction, and the argument that settled it. It also reports a rule this author shipped one increment earlier which turns out to be stricter than the property it enforces, excluding ten of twenty-four cases for no reason. No test found that. It surfaced while gathering data for this article. How to read this The general argument is in the opening, in the section called The Argument That Settled It, and in Pattern Extraction. Those three need nothing but attention. The sections between them work the argument through a real case with real numbers, and they use the vocabulary of the trade. Every term is glossed at first use, but a reader who wants the r ## Actegories DevFeed: [Actegories]() Original publisher: [Read original article]() Author: Bartosz Milewski Published: 2026-06-30T11:45:46Z Content type: tutorial Language: en Sources: [Bartosz Milewski's Programming Cafe]() Topics: [Programming](), [Haskell](), [Code]() Tags: [actegories](), [category-theory](), [class](), [haskell](), [lens](), [optics](), [programming](), [types]() ### AI overview This tutorial introduces actegories, explaining their relationship to monoidal categories and their role in programming optics such as lenses, prisms, and traversals. It develops the concepts through Haskell models, including tensor products, unit objects, constraints, associators, unitors, and categorical actions. ### Source excerpt Previously: Kan Extensions in Double Categories. In programming, actegories play a central role in optics: lenses, prisms, traversals, etc. To understand actegories, let's start with the definition of a monoidal category. Monoidal Category A monoidal category is a category equipped with a tensor product. A tensor product is a functor . We assume that this [...] ## PHPStan custom rules DevFeed: [PHPStan custom rules]() Original publisher: [Read original article]() Author: Rob Published: 2026-03-03T11:00:00Z Content type: tutorial Language: en Sources: [Rob Allen]() Topics: [PHP](), [Exception](), [Code](), [phpstorm]() Tags: [autocomplete](), [class](), [code](), [container](), [exception](), [extension](), [php](), [phpstorm](), [runtime](), [settings]() ### AI overview This tutorial explains how a PHPStan custom rule can detect references to unavailable PHP classes. It also describes configuring PhpStorm to limit autocomplete to extensions used by the application. ### Source excerpt Recently I discovered that this code passed our PHPStan level 10 checks: use http\Exception\InvalidArgumentException; // ... throw new InvalidArgumentException; I was surprised as http\Exception\InvalidArgumentException is not a class in our system. While cooling, I discovered that there's an http PHP extension and it appears that PHPStan has a stub for this which means that it accepts it as existing even if it doesn't. What we think happened is that I wrote throw new InvalidArgumentException; and... continue reading. ## 12 OOP Concepts EVERY Developer Should Know DevFeed: [12 OOP Concepts EVERY Developer Should Know]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-02-12T04:27:26Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Object-oriented programming (OOP)](), [Programming](), [Code](), [interfaces](), [Polymorphism](), [App]() Tags: [class](), [classes](), [code](), [concepts](), [developer](), [interface](), [interfaces](), [object-oriented](), [oop](), [practical](), [programming](), [real-world]() ### AI overview An introductory tutorial on object-oriented programming explains how classes, objects, and interfaces organize state and behavior. It uses real-world examples such as users, orders, payments, and payment gateways, and notes that these concepts are relevant to low-level design interviews. ### Source excerpt Key Object-Oriented Programming Concepts ## Creating an Arduino Library for ESP32 DevFeed: [Creating an Arduino Library for ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2025-12-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Arduino](), [ESP32](), [Library](), [Development](), [Code](), [C++](), [ide](), [Programming](), [API]() Tags: [arduino](), [arduino-ide](), [beginner](), [blog](), [c-plus-plus](), [class](), [classes](), [code](), [development](), [esp32](), [getting-started](), [guide](), [how-to](), [ide](), [libraries](), [library](), [maintainability](), [modular](), [modularity](), [modules](), [programming](), [structure](), [tutorial]() ### AI overview A step-by-step guide to creating, structuring, and publishing custom Arduino libraries for ESP32. It explains library benefits and structure, prerequisites, and implementation through a minimal "Hello World" example. ### Source excerpt Learn how to create, structure, and publish Arduino libraries for ESP32. This step-by-step guide covers everything from understanding a library structure to submitting your library to the Arduino Library Manager. ## Empowering Your Annotations with Fields DevFeed: [Empowering Your Annotations with Fields]() Original publisher: [Read original article]() Author: Peter Lawrey (noreply@blogger.com) Published: 2024-12-21T22:13:00Z Content type: tutorial Language: en Sources: [Vanilla Java]() Topics: [Java](), [Java Language](), [Code](), [interfaces](), [enum]() Tags: [class](), [code](), [enum](), [info](), [interfaces](), [java](), [java-language](), [opinion]() ### AI overview This tutorial explains how Java annotations can contain nested classes, interfaces, enums, other annotations, static fields, and embedded logic. It discusses uses such as domain converters, framework lifecycle hooks, and syntactic sugar, while noting that excessive nesting can reduce readability. ### Source excerpt Introduction Java's annotation system has come a long way since its introduction in Java 5. At first glance, annotations appear to be mere metadata markers on classes and methods. However, annotations can do much more than that. You can nest types within them, incorporate fields that reference helper classes, and even embed logic via static singletons. These capabilities provide a powerful mechanism for integrating domain-specific or framework-specific functionality right into your code, in ways that are both compact and self-documenting. Why Add Code to Annotations? The Java language specification usually treats annotations as static metadata describing a type, method, field, or parameter. However, you can leverage nested classes (including enums, interfaces, and even other annotations) to extend the functionality of a single annotation. This approach allows you to keep logic closely tied to the metadata, rather than scattering it across multiple classes. Common use cases include: Custom domain converters. For example, if you have a long that needs to be stored in an encoded format (e.g., Base85), you can supply a default converter directly within the annotation. Framework-specific lifecycle hooks. You can embed an interface for processing the annotation, enabling the framework to perform reflective lookups and apply behaviour at runtime. Syntactic sugar. Rather than writing @LongConversion(SomeConverter.class), you could write @ShortText, which internally references a known converter. Nesting Types in Java You can nest various kinds of types within your classes or annotations--these include interfaces, enums, classes, and even other annotations. Although nesting these types can feel unconventional, it is fully supported by the language. For example: public class A { public interface B { public enum C { ; public @interface D { public class E { // etc etc } } } } } While this example might look bizarre, it demonstrates the power and flexibility of Java's nesting rule ## A Curious Case of Mistaken Identity: How Lambdas Break Data Class Hashing DevFeed: [A Curious Case of Mistaken Identity: How Lambdas Break Data Class Hashing]() Original publisher: [Read original article]() Author: Matt McKenna Published: 2024-11-14T21:44:31Z Content type: tutorial Language: en Sources: [Matt McKenna]() Topics: [Kotlin](), [hashing](), [hash](), [consistency]() Tags: [android](), [behavior](), [class](), [data-class](), [hashcode](), [hashing](), [kotlin](), [maintenance]() ### AI overview This Kotlin article explains why data class instances containing lambdas may compare as unequal and produce different hash-based behavior. Each lambda instance has a distinct identity, so the article recommends excluding the callback from equality and hashCode calculations, while noting the resulting maintenance cost. ### Source excerpt Introduction: The Scene of the Crime It was a dark and stormy night. My hands were flying across the keys when suddenly the codebase began to exhibit strange behavior. Hashes, which once returned the same values for identical objects, suddenly became... ## Replace Useless Cases with Interfaces DevFeed: [Replace Useless Cases with Interfaces]() Original publisher: [Read original article]() Published: 2024-08-15T00:00:00Z Content type: article Language: en Sources: [Donovan LaDuke - Developer]() Topics: [Code](), [mvc](), [Framework]() Tags: [architecture](), [class](), [dependencies](), [function](), [implement](), [interface](), [interfaces]() ### AI overview The article presents an alternative to dedicated pass-through use-case classes: define use-case interfaces and implement them directly in the repository. This preserves architectural benefits while reducing unnecessary code. It also discusses using invoke-operator extensions and the resulting trade-off of exposing an additional function. ### Source excerpt An alternative approach to avoiding Useless Cases by making Use Case interfaces without dedicated Use Case classes ## Avoid the Long Parameter List DevFeed: [Avoid the Long Parameter List]() Original publisher: [Read original article]() Author: Google Testing Bloggers (noreply@blogger.com) Published: 2024-05-20T13:42:00Z Content type: tutorial Language: en Sources: [Google Testing Blog]() Topics: [Code](), [Java](), [C++](), [Kotlin](), [Python]() Tags: [c-plus-plus](), [class](), [code](), [code-health](), [data-class](), [gene-volovich](), [google](), [java](), [kotlin](), [language](), [list](), [parameter](), [post](), [python](), [series](), [tott]() ### AI overview This Google Code Health article explains how long parameter lists make method calls difficult to understand and maintain. It recommends grouping related parameters into meaningful value objects, with language-specific options including Java records, Kotlin data classes, C++ option structs, Python keyword arguments and defaults, and the Java Builder pattern. ### Source excerpt This is another post in our Code Health series. A version of this post originally appeared in Google bathrooms worldwide as a Google Testing on the Toilet episode. You can download a printer-friendly version to display in your office. By Gene Volovich Have you seen code like this? void transform(String fileIn, String fileOut, String separatorIn, String separatorOut); This seems simple enough, but it can be difficult to remember the parameter ordering. It gets worse if you add more parameters (e.g., to specify the encoding, or to email the resulting file): void transform(String fileIn, String fileOut, String separatorIn, String separatorOut, String encoding, String mailTo, String mailSubject, String mailTemplate); To make the change, will you add another (overloaded) transform method? Or add more parameters to the existing method, and update every single call to transform? Neither seems satisfactory. One solution is to encapsulate groups of the parameters into meaningful objects. The CsvFile class used here is a "value object" -- simply a holder for the data. class CsvFile { CsvFile(String filename, String separator, String encoding) { ... } String filename() { return filename; } String separator() { return separator; } String encoding() { return encoding; } } // ... and do the same for the EmailMessage class void transform(CsvFile src, CsvFile target, EmailMessage resultMsg) { ... } How to define a value object varies by language. For example, in Java, you can use a record class, which is available in Java 16+ (for older versions of Java, you can use AutoValue to generate code for the value object); in Kotlin, you can use a data class; in C++, you can use an option struct. Using a value object this way may still result in a long parameter list when instantiating it. Solutions for this vary by language. For example, in Python, you can use keyword arguments and default parameter values to shorten the parameter list; in Java, one option is to use the Builder pattern, wh ## Item 29: Minimize elements' visibility DevFeed: [Item 29: Minimize elements' visibility]() Original publisher: [Read original article]() Published: 2024-05-06T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [interface](), [Kotlin](), [class](), [properties](), [maintenance]() Tags: [class](), [how-to](), [interface](), [kotlin](), [maintenance](), [properties](), [workshop-learning-programming]() ### AI overview The article explains why APIs should minimize visible elements: smaller interfaces are easier to learn, maintain, test, and change. It also shows how restricting visibility in Kotlin helps protect class invariants by encapsulating internal state, including making property setters private. ### Source excerpt Why we should minimize elements' visibility and how to do it. ## Kotlin Reflection: Class references DevFeed: [Kotlin Reflection: Class references]() Original publisher: [Read original article]() Published: 2023-10-23T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [class]() Tags: [class](), [example](), [kotlin](), [object](), [practical](), [workshop-learning-programming]() ### AI overview A tutorial on Kotlin class references, covering class names, type characteristics, visibility, members, and declared members, with a practical object serialization example. ### Source excerpt All the essential aspects of class references, and a practical object serialization example. ## Data Classes and Destructuring DevFeed: [Data Classes and Destructuring]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2023-10-09T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Kotlin](), [data]() Tags: [class](), [classes](), [copy](), [data-class](), [destructuring](), [destructuring-assignment](), [equals](), [hashcode](), [introduction](), [kotlin](), [learn-to-program](), [object](), [open](), [operator](), [override](), [programming](), [properties](), [tostring]() ### AI overview A Kotlin tutorial introducing data classes and destructuring. It explains how data classes relate to equals(), hashCode(), and toString(), beginning with reference equality and overriding inherited functions. ### Source excerpt At the end of the last chapter, we saw how all objects in Kotlin inherit three functions from an open class called Any. Those functions are equals(), hashCode(), and toString(). In this chapter, we're going to learn about data classes, which are super-powered classes that are especially helpful when we've got an immutable class that mainly just holds properties. To better understand data classes, let's first explore each of the three functions above, and see what's involved when we override them! ## Touchlab Open Source Updates - Sep 2023 - Touchlab Engineering DevFeed: [Touchlab Open Source Updates - Sep 2023 - Touchlab Engineering]() Original publisher: [Read original article]() Published: 2023-09-19T23:33:27Z Content type: news Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [multiplatform](), [Kotlin](), [iOS](), [Coroutines](), [Logging](), [Crashlytics](), [Code]() Tags: [class](), [concurrency](), [coroutines](), [crashlytics](), [default-parameters](), [engineering](), [enums](), [ios](), [kmp](), [kotlin](), [logging](), [multiplatform](), [open-source](), [sealed](), [updates]() ### AI overview Touchlab reports open-source updates for Kotlin Multiplatform, including SKIE improvements for Kotlin-to-iOS interfaces, the Kermit 2.0 release, CrashKiOS updates, and Stately 2.0 concurrency features. ### Source excerpt Touchlab has pushed some major open source updates over the past few weeks that will have an impact on how teams use KMP, and on KMP adoption overall. Here are the highlights. ## Objects in Kotlin DevFeed: [Objects in Kotlin]() Original publisher: [Read original article]() Published: 2023-07-17T00:01:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [object](), [class](), [constructor](), [interfaces]() Tags: [class](), [constructor](), [interfaces](), [kotlin](), [object](), [synchronization](), [syntax](), [workshop-learning-programming]() ### AI overview This Kotlin tutorial explains how to create objects with object expressions and object declarations. It covers anonymous objects, inheritance and interface implementation, object scope, singleton behavior, and practical uses such as listeners and synchronization locks. ### Source excerpt What is object expression, object declaration and companion objects, and how we use them. ## Building a Note-Taking App in Compose DevFeed: [Building a Note-Taking App in Compose]() Original publisher: [Read original article]() Author: Doximity Published: 2023-07-05T19:47:00Z Content type: tutorial Language: en Sources: [Doximity]() Topics: [Jetpack Compose](), [App](), [Code](), [Template]() Tags: [app](), [architecture](), [build](), [building](), [class](), [clean-architecture](), [code](), [collect](), [compose](), [data-class](), [di](), [extension-function](), [flow](), [icons](), [implement](), [koin](), [list](), [state](), [state-management](), [view]() ### AI overview A case study showing how to build a note-taking app with Jetpack Compose. It models note state, renders the notes UI, collects note data through a presenter and Clean Architecture use cases, and plans events for adding, editing, checking, and deleting notes. ### Source excerpt In this case study, we will build a note-taking app that lets the user add, edit and delete notes. It uses Compose for both the view and presentation layers! Note: This is a follow up to Part 1: Simplifying State Management with Compose and assumes the reader is already familiar with Jetpack Compose. The Template I find it useful to start with the model that represents the state of the screen we're building. It will have a list of notes, with each note containing properties for the text and checkbox: data class NotesUiModel(val notes: List) : UiModel { data class Note(val text: String, val isChecked: Boolean) : UiModel } It'll be the job of the presenter to produce this model. Initially, let's implement a stub to return an empty list of notes (we'll ignore parameters for now): class NotesListPresenter : Presenter { @Composable override fun present(params: Unit): NotesUiModel { return NotesUiModel(notes = emptyList()) } } Then we can build our view to render the model that's returned by the presenter: @Composable fun NotesScreen() { val presenter: NotesListPresenter = koinInject() // we use koin for DI val uiModel = presenter.present(Unit) Column { TopAppBar(title = { Text("Notes") }) Notes(uiModel) } } } The View The views themselves are pretty self-explanatory if you're already familiar with building UIs in Compose. For the notes, we'll take in a NotesUiModel argument and create a LazyColumn with the notes property. A FAB button is used for adding new notes, although we'll skip the triggering of events and return to this part in a little bit: @Composable private fun Notes(uiModel: NotesUiModel) { Box { LazyColumn { items(uiModel.notes) { note -> Note(note) } } FloatingActionButton(onClick = { /* TODO */ }) { Icon(imageVector = Icons.Rounded.Add) } } } Then we can render each note with a checkbox, text field and delete button: @Composable private fun Note(uiModel: Note) { Row { Checkbox( checked = uiModel.isChecked, onCheckedChange = { /* T ## Avoid Java double brace initialization DevFeed: [Avoid Java double brace initialization]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2023-06-27T20:58:00Z Content type: tutorial Language: en Sources: [Py's blog]() Topics: [Java](), [Code](), [Android]() Tags: [android](), [class](), [classes](), [code](), [constructor](), [crash-reporting](), [gc](), [global](), [implementation](), [java](), [leak](), [leakcanary](), [lifecycle](), [memory](), [memory-leak](), [object](), [patterns](), [subclass]() ### AI overview This tutorial explains how Java double brace initialization can cause memory leaks. An anonymous HashMap subclass implicitly retains its outer Activity, so a breadcrumb stored by a singleton BugSnag client can keep a destroyed Android Activity in memory. The article recommends avoiding the pattern and using explicit initialization or Kotlin. ### Source excerpt TL;DR Avoid doing this: new HashMap() {{ put("key", value); }}; Leak Trace I was recently looking at the following leak trace from LeakCanary: ┬─── │ GC Root: Global variable in native code │ ├─ com.bugsnag.android.AnrPlugin instan... ## Class Modifiers in Dart: Sealed, Interface, Base DevFeed: [Class Modifiers in Dart: Sealed, Interface, Base]() Original publisher: [Read original article]() Author: Marvin März Published: 2023-06-23T11:29:43Z Content type: tutorial Language: en Sources: [QuickBird Studios Blog]() Topics: [Dart](), [Object-oriented programming (OOP)]() Tags: [abstract-class](), [class](), [classes](), [dart](), [flutter](), [implementation](), [interface](), [oop](), [pattern-matching](), [post](), [sealed](), [sealed-interface]() ### AI overview This tutorial explains Dart 3 class modifiers, including the newly introduced sealed, interface, final, and base modifiers and changes to existing modifiers. It describes how modifiers control whether classes can be extended, mixed in, constructed, or implemented, and discusses their practical use cases. ### Source excerpt With Dart 3 the class modifiers sealed, interface, final and base were introduced into the Dart language. They also updated how existing ones work. In this article, we show you why this change was made and how those new modifiers work. The post Class Modifiers in Dart: Sealed, Interface, Base appeared first on QuickBird Studios. ## MutexProtected: A C++ Pattern for Easier Concurrency DevFeed: [MutexProtected: A C++ Pattern for Easier Concurrency]() Original publisher: [Read original article]() Author: Andreas Kling Published: 2023-04-06T00:00:00Z Content type: tutorial Language: en Sources: [Andreas Kling]() Topics: [C++](), [Concurrency](), [Programming](), [Code](), [Deadlock]() Tags: [c-plus-plus](), [callback](), [class](), [concurrency](), [cpp](), [locks](), [mutex](), [programming](), [serenityos](), [technical](), [type-system]() ### AI overview This tutorial explains the MutexProtected pattern, which combines a mutex and protected data behind a callback-based C++ API. It compares manual locking in C with C++ RAII and the newer pattern, showing how the design reduces forgotten-lock errors and encodes the mutex-data relationship in the type system. It also notes that inconsistent ordering of multiple MutexProtected instances can still cause deadlocks. ### Source excerpt In this post, we will discuss the challenges of programming with locks and how the C++ language offers some useful tools to make it easier. We will start with an example in C and then use C++ to improve upon it in steps. The example APIs are based on real-life APIs from the SerenityOS kernel. ## Enum classes in Kotlin DevFeed: [Enum classes in Kotlin]() Original publisher: [Read original article]() Published: 2023-02-01T00:01:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [enum class](), [Kotlin]() Tags: [abstract-class](), [class](), [constructor](), [enum](), [enum-class](), [enums](), [kotlin](), [property](), [superclass](