From 60a076ac9cc2c0fe06055e36b54b9912e93215d4 Mon Sep 17 00:00:00 2001 From: Eideren Date: Wed, 19 Jun 2024 15:32:38 +0200 Subject: [PATCH] Update flexible-processing.md Forgot to fix these --- .../engine/entity-component-system/flexible-processing.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/en/manual/engine/entity-component-system/flexible-processing.md b/en/manual/engine/entity-component-system/flexible-processing.md index b83d289e4..235446cd3 100644 --- a/en/manual/engine/entity-component-system/flexible-processing.md +++ b/en/manual/engine/entity-component-system/flexible-processing.md @@ -37,7 +37,7 @@ The main difference compared to [`EntityProcessor`](xref:Stride.Engine.EntityPro is that [`IComponent`](xref:Stride.Engine.FlexibleProcessing.IComponent`2) is not limited to concrete types, your processor may operate on interfaces as well; ```cs // Here, declaring the interface, which will be the type received by the processor -public interface IInteractable : IComponent +public interface IInteractable : IComponent { void Interact(); public class InteractableProcessor : IProcessor @@ -47,7 +47,7 @@ public interface IInteractable : IComponent ## Performance While it is more flexible, processing components as interfaces instead of concrete class may introduce some overhead. -If the system you're writing is performance critical you should look into strategies to elide or reduce virtual calls in your hot path. \ No newline at end of file +If the system you're writing is performance critical you should look into strategies to elide or reduce virtual calls in your hot path.