Content deleted Content added
Undid revision 1183477772 by SOLARSCUFFLEBOT (talk). This page is about "Data-Oriented Design" and not "Data-Oriented Programming". |
Undid revision 1177960743 by 2A01:5241:2A0:1800:ED1F:3F05:70C8:99A9 (talk) This page is about "Data-Oriented Design" and not "Data-Oriented Programming". |
||
Line 1:
{{Short description|Program optimization approach in computing
{{Distinguish|Data-driven programming}}
{{Distinguish|Data-oriented programming}}
{{More citations needed|date=July 2020}}
As a design paradigm, '''data-oriented-design''' focuses on optimal transformations of data and focuses on modelling programs as '''transforms.''' Transforms are abstractions of code that solely focus on the mapping of inputs to outputs. They do not distinguish between accessing inputs by [[Parameter (computer programming)|parameter]], [[Pointer (computer programming)|pointer]], [[Reference (computer science)|reference]], [[upvalue]], and vice versa with writing outputs. This eliminates the concept of a [[Side effect (computer science)|Side-effect]] and focuses solely on how inputs transform into outputs, logically identical to [[Function (mathematics)|functions]] in mathematics.
|