#Programming_paradigms : #Functional programming
Seeks to use pure functions.
Pure functions:
• have no side effects
• return a value that depends only on their arguments. e.g.
• are easier to reason about and test.
• are more efficient. Once the function has been evaluated for an input, the result can be stored and referred to the next time the function of that input is needed, reducing the number of times the function is called. This is called #memoization.
• are less confusing to run in parallel (See #concurrent programming).
Using only pure functions complicates the otherwise simple task of IO since this appears to inherently require side effects.
Seeks to use pure functions.
Pure functions:
• have no side effects
• return a value that depends only on their arguments. e.g.
sin(x) will, for the same value of x, always return the same result.• are easier to reason about and test.
• are more efficient. Once the function has been evaluated for an input, the result can be stored and referred to the next time the function of that input is needed, reducing the number of times the function is called. This is called #memoization.
• are less confusing to run in parallel (See #concurrent programming).
Using only pure functions complicates the otherwise simple task of IO since this appears to inherently require side effects.
#Atomic_operations also linearizable, indivisible or uninterruptible
In #concurrent programming, an operation or set of operations is atomic if it appears to the rest of the system to occur at once without being interrupted.
Atomic operations commonly have a succeed-or-fail definition. They either successfully change the state of the system, or have no apparent effect.
In #concurrent programming, an operation or set of operations is atomic if it appears to the rest of the system to occur at once without being interrupted.
Atomic operations commonly have a succeed-or-fail definition. They either successfully change the state of the system, or have no apparent effect.
#language #D
D
- is a system programming language first appeared in 2001. Though it originated as a re-engineering of C++, D is a distinct language, having redesigned some core C++ features while also taking inspiration from other languages, notably Java, Python, Ruby, C#, and Eiffel.
D attempts to combine the performance and safety of compiled languages with the expressive power of modern dynamic languages. Idiomatic D code is commonly as fast as equivalent C++ code, while being shorter and memory-safe. Type inference, automatic memory management and syntactic sugar for common types allow faster development, while bounds checking, design by contract features and a concurrency-aware type system help reduce the occurrence of bugs.
Paradigms: #imperative, #object_oriented, #metaprogramming, #functional and #concurrent (actor model)
Comparison with C
Despite their difference, D has been constrained in its design by the rule that any code that is legal in both C and D should behave in the same way.
Comparison with C++
Things D gained before C++:
• closures
• anonymous functions
• compile time function execution
Things D adds:
• design by contract
• unit testing
• true modules
• garbage collection
• first class arrays
• associative arrays
• dynamic arrays
• array slicing
• nested functions
• lazy evaluation
• built-in support for documentation comments, allowing automatic documentation generation
Things D replaces:
• multiple inheritance is replaced by Java-style single inheritance with interfaces and mixins.
• template syntax is re-engineered
Things they have in common:
• D's declaration, statement and expression syntax closely matches that of C++.
• D retains C++'s ability to perform low-level coding and to add inline assembler. The inline assembler typifies the differences between D and application languages like Java and C#. An inline assembler lets programmers enter machine-specific assembly code within standard D code, a method often used by system programmers to access the low-level features of the processor needed to run programs that interface directly with the underlying hardware, such as operating systems and device drivers.
Docs: https://dlang.org/spec/spec.html
D
- is a system programming language first appeared in 2001. Though it originated as a re-engineering of C++, D is a distinct language, having redesigned some core C++ features while also taking inspiration from other languages, notably Java, Python, Ruby, C#, and Eiffel.
D attempts to combine the performance and safety of compiled languages with the expressive power of modern dynamic languages. Idiomatic D code is commonly as fast as equivalent C++ code, while being shorter and memory-safe. Type inference, automatic memory management and syntactic sugar for common types allow faster development, while bounds checking, design by contract features and a concurrency-aware type system help reduce the occurrence of bugs.
Paradigms: #imperative, #object_oriented, #metaprogramming, #functional and #concurrent (actor model)
Comparison with C
Despite their difference, D has been constrained in its design by the rule that any code that is legal in both C and D should behave in the same way.
Comparison with C++
Things D gained before C++:
• closures
• anonymous functions
• compile time function execution
Things D adds:
• design by contract
• unit testing
• true modules
• garbage collection
• first class arrays
• associative arrays
• dynamic arrays
• array slicing
• nested functions
• lazy evaluation
• built-in support for documentation comments, allowing automatic documentation generation
Things D replaces:
• multiple inheritance is replaced by Java-style single inheritance with interfaces and mixins.
• template syntax is re-engineered
Things they have in common:
• D's declaration, statement and expression syntax closely matches that of C++.
• D retains C++'s ability to perform low-level coding and to add inline assembler. The inline assembler typifies the differences between D and application languages like Java and C#. An inline assembler lets programmers enter machine-specific assembly code within standard D code, a method often used by system programmers to access the low-level features of the processor needed to run programs that interface directly with the underlying hardware, such as operating systems and device drivers.
Docs: https://dlang.org/spec/spec.html