Difference between revisions of "Open research problems"

From HaskellWiki
Jump to: navigation, search
m
m
 
Line 14: Line 14:
 
=== I/O ===
 
=== I/O ===
  
:See [[Open_research_problems/The_I/O_quandary|the I/O quandary]].
+
:See [[The I/O problem|the I/O problem]].
  
 
== Specific problems ==
 
== Specific problems ==

Latest revision as of 12:50, 31 May 2022


General problems

Efficiency of lazy functional languages

This is a problem that came up during IRC discussions. We consider a purely functional language L:
  • By "purely functional" we mean a language that has value semantics; that is, there is no function such that after evaluation of the function the value that was referred to by something else changed. (Also known as "No Side Effects").
  • A value is "changed" when it is not the case during an evaluation that when the old value and the new value would both be fully evaluated, there wouldn't be the same result. This should make sure that laziness is allowed in the purely functional language.

Can purely functional languages like L can implement all algorithms that can be implemented in a language like C as efficiently in an amortized sense, ignoring space-usage?

I/O

See the I/O problem.

Specific problems

Implement encapsulated-state interface entirely in Haskell (no primitives)

Implement Data.STRef and Control.Monad.ST.runST without using the built-in monadic ST or IO types. This needs to happen with operations that all run in O(1) amortized time.