Jaroslav Tulach 735053c218 Implementing basic functions (#3554) ... The language specification suggests to add [five basic functions into the standard library](https://github.com/enso-org/design/blob/wip/wd/enso-spec/epics/enso-spec-1.0/05.%20Functions.md#useful-functions-in-the-standard-library). `identity`, `flip`, `const`, `curry` & `uncurry`. # Important Notes The new functions are being added into existing `Function.enso` file. That may not be the best place, but it is not clear from the [design spec](https://github.com/enso-org/design/blob/wip/wd/enso-spec/epics/enso-spec-1.0/05.%20Functions.md#useful-functions-in-the-standard-library) how they are supposed to be imported. I can move them wherever needed. There is a documentation provided for each of the functions, but I am not sure how to verify it is correct. Do we generate the documentation for stdlib somehow?		2022-07-11 10:30:44 +00:00
..
bin	Enso Integration with Ideal Graph Visualizer (#3533)	2022-06-23 04:43:49 +00:00
engine/THIRD-PARTY	Profile the language server (#3389)	2022-05-10 12:44:05 +00:00
launcher	Frgaal integration in sbt (#3421)	2022-05-04 21:18:40 +02:00
lib/Standard	Implementing basic functions (#3554)	2022-07-11 10:30:44 +00:00
project-manager/THIRD-PARTY	Frgaal integration in sbt (#3421)	2022-05-04 21:18:40 +02:00
enso.bundle.template	Better component handling in the project manager (#1399)	2021-01-15 15:26:51 +00:00
launcher-manifest.yaml	Bump the development version number (#1389)	2021-01-06 08:57:02 +00:00
manifest.template.yaml	Bump Minimal PM/Launcher Versions for New Engine (#1854)	2021-07-13 13:08:00 +02:00