Add examples to document features

[IR0NSIGHT]

No description provided.

[b-studios]

Thank you for your contributions! Here are a few remarks before we can merge this:

1. we typically do not have single files in the examples folder (which in all honesty is our tests folder). Maybe the features folder might be suitable? What features do you want to demonstrate? How would you call the files
2. to automatically run the files and check whether our compiler still works, all files have to have a .check file with the expected println output. If you don't print anything, the file can be empty.
3. we don't have a styleguide, but indent all Effekt files with 2 spaces. I'll also add a few more stylistic comments in the review.

[b-studios]

Suggested change

	//will save name to database
	// will save name to database

why "name"?

[b-studios]

Suggested change

	db.addEntry(newStudent("Max","Marschall"));
	db.addEntry(newStudent("Max", "Marschall"));

[b-studios]

Is the type annotation necessary?

[b-studios]

Suggested change

	def makeNewDB(){ r: Region }:DataBase[Student] at { r } = {
	def makeNewDB { r: Region }: DataBase[Student] at { r } = {

[b-studios]

Suggested change

	//create database instance
	// create database instance

[b-studios]

Again, is the type annotation necessary?

[b-studios]

Suggested change

	names.foreach(){ name => println(name); ()}
	names.foreach { name => println(name) }

[b-studios]

Suggested change

	def getEntries() = {
	return names;
	}
	def getEntries() = names

[b-studios]

Suggested change

	def fb2 = makeNewDB(){ r };
	def fb2 = makeNewDB {r};

Typically we omit empty value sections

[b-studios]

printing the time in a "test" is difficult because you don't know what the expected result will be

[b-studios]

I am writing such detailed review comments since it would be great if you could also apply them to Effekt code that you write in general :)