#functionallanguages — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #functionallanguages, aggregated by home.social.
-
Do any of y'all have conference swag that you won't let go?
This clojure/conj shirt of mine from 2013 comes to mind
-
Do any of y'all have conference swag that you won't let go?
This clojure/conj shirt of mine from 2013 comes to mind
-
Do any of y'all have conference swag that you won't let go?
This clojure/conj shirt of mine from 2013 comes to mind
-
Do any of y'all have conference swag that you won't let go?
This clojure/conj shirt of mine from 2013 comes to mind
-
Do any of y'all have conference swag that you won't let go?
This clojure/conj shirt of mine from 2013 comes to mind
-
I love local functions in scheme. Need a helper function that's only relevant inside of exactly one function? You can make it only exist in that one function.
And then if you need it in mulitple functions, you can trivially pass it around as an argument without any shenanigans with pointers or references or whatever. Just pass it.
Need the function to be mutated to better suit where its used? You can do that. Functions are really just any other data you'd send somewhere.
I find a lot of stuff I try to do maps directly to language constructs with so much less boilerplate code than in C++ or something like that. Not everything, a conceptually iterative process is sometimes a little confusing, and recursion can get weird, still, I like it. #programming #scheme #functionallanguages -
I love local functions in scheme. Need a helper function that's only relevant inside of exactly one function? You can make it only exist in that one function.
And then if you need it in mulitple functions, you can trivially pass it around as an argument without any shenanigans with pointers or references or whatever. Just pass it.
Need the function to be mutated to better suit where its used? You can do that. Functions are really just any other data you'd send somewhere.
I find a lot of stuff I try to do maps directly to language constructs with so much less boilerplate code than in C++ or something like that. Not everything, a conceptually iterative process is sometimes a little confusing, and recursion can get weird, still, I like it. #programming #scheme #functionallanguages -
I love local functions in scheme. Need a helper function that's only relevant inside of exactly one function? You can make it only exist in that one function.
And then if you need it in mulitple functions, you can trivially pass it around as an argument without any shenanigans with pointers or references or whatever. Just pass it.
Need the function to be mutated to better suit where its used? You can do that. Functions are really just any other data you'd send somewhere.
I find a lot of stuff I try to do maps directly to language constructs with so much less boilerplate code than in C++ or something like that. Not everything, a conceptually iterative process is sometimes a little confusing, and recursion can get weird, still, I like it. #programming #scheme #functionallanguages -
I love local functions in scheme. Need a helper function that's only relevant inside of exactly one function? You can make it only exist in that one function.
And then if you need it in mulitple functions, you can trivially pass it around as an argument without any shenanigans with pointers or references or whatever. Just pass it.
Need the function to be mutated to better suit where its used? You can do that. Functions are really just any other data you'd send somewhere.
I find a lot of stuff I try to do maps directly to language constructs with so much less boilerplate code than in C++ or something like that. Not everything, a conceptually iterative process is sometimes a little confusing, and recursion can get weird, still, I like it. #programming #scheme #functionallanguages -
I love local functions in scheme. Need a helper function that's only relevant inside of exactly one function? You can make it only exist in that one function.
And then if you need it in mulitple functions, you can trivially pass it around as an argument without any shenanigans with pointers or references or whatever. Just pass it.
Need the function to be mutated to better suit where its used? You can do that. Functions are really just any other data you'd send somewhere.
I find a lot of stuff I try to do maps directly to language constructs with so much less boilerplate code than in C++ or something like that. Not everything, a conceptually iterative process is sometimes a little confusing, and recursion can get weird, still, I like it. #programming #scheme #functionallanguages -
Upgrading Julia packages
https://technologytales.com/2024/01/23/upgrading-julia-packages/
#DataScience #Linux #Mac #Programming #Scripting #Software #UNIX #Windows #CrossplatformSoftware #ElectronShell #FunctionalLanguages #Julia #ObjectorientedProgrammingLanguages #PackageManager #PKG #ProceduralProgrammingLanguages #ScriptingLanguage #ScriptingLanguages #Subshell #WindowsPackageManager
-
Upgrading Julia packages
https://technologytales.com/2024/01/23/upgrading-julia-packages/
#DataScience #Linux #Mac #Programming #Scripting #Software #UNIX #Windows #CrossplatformSoftware #ElectronShell #FunctionalLanguages #Julia #ObjectorientedProgrammingLanguages #PackageManager #PKG #ProceduralProgrammingLanguages #ScriptingLanguage #ScriptingLanguages #Subshell #WindowsPackageManager
-
On line, on the #Codemotion site, my talk immodestly titled "The Anatomy of a Functional Language (a hommage to a great book on Lisp): you may find the link in the first comment.
The talk draws inspiration from a jewel in computer science history, a paper by Peter J Landin written six decades ago: "The mechanical evaluation of expressions", where closures were introduced.
To introduce the basic features of functional languages and show how they can be naively implemented, I designed a language called Awful (A Weird FUnctional Language) and developed an interpreter for it, you may check it on github (see link in the comments to this post).
The talk is in my macaroni-English and the code is written in my macaroni-Python: however I wrote a more serious interpreter in C and a markdown text where I essentially explain better and with more details what I've tried to communicate in the talk.
Enjoy!
#ProgrammingLanguages
#FunctionalLanguagesThe talk:
https://talks.codemotion.com/the-anatomy-of-a-functional-languageA functional languages tutorial derived from the talk:
https://github.com/pcaressa/awful/blob/main/doc/awful_intro_fl.mdThe repository with the Afwul interpreter:
https://github.com/pcaressa/awful -
On line, on the #Codemotion site, my talk immodestly titled "The Anatomy of a Functional Language (a hommage to a great book on Lisp): you may find the link in the first comment.
The talk draws inspiration from a jewel in computer science history, a paper by Peter J Landin written six decades ago: "The mechanical evaluation of expressions", where closures were introduced.
To introduce the basic features of functional languages and show how they can be naively implemented, I designed a language called Awful (A Weird FUnctional Language) and developed an interpreter for it, you may check it on github (see link in the comments to this post).
The talk is in my macaroni-English and the code is written in my macaroni-Python: however I wrote a more serious interpreter in C and a markdown text where I essentially explain better and with more details what I've tried to communicate in the talk.
Enjoy!
#ProgrammingLanguages
#FunctionalLanguagesThe talk:
https://talks.codemotion.com/the-anatomy-of-a-functional-languageA functional languages tutorial derived from the talk:
https://github.com/pcaressa/awful/blob/main/doc/awful_intro_fl.mdThe repository with the Afwul interpreter:
https://github.com/pcaressa/awful -
On line, on the #Codemotion site, my talk immodestly titled "The Anatomy of a Functional Language (a hommage to a great book on Lisp): you may find the link in the first comment.
The talk draws inspiration from a jewel in computer science history, a paper by Peter J Landin written six decades ago: "The mechanical evaluation of expressions", where closures were introduced.
To introduce the basic features of functional languages and show how they can be naively implemented, I designed a language called Awful (A Weird FUnctional Language) and developed an interpreter for it, you may check it on github (see link in the comments to this post).
The talk is in my macaroni-English and the code is written in my macaroni-Python: however I wrote a more serious interpreter in C and a markdown text where I essentially explain better and with more details what I've tried to communicate in the talk.
Enjoy!
#ProgrammingLanguages
#FunctionalLanguagesThe talk:
https://talks.codemotion.com/the-anatomy-of-a-functional-languageA functional languages tutorial derived from the talk:
https://github.com/pcaressa/awful/blob/main/doc/awful_intro_fl.mdThe repository with the Afwul interpreter:
https://github.com/pcaressa/awful -
Some pictures from my last talk at #Codemotion Milan Conference: thanks to the organizers for the invitation, the audience for the patience and the interesting questions.
The code of the interpreter and compiler I've discussed is here: https://github.com/pcaressa/awful
-
Some pictures from my last talk at #Codemotion Milan Conference: thanks to the organizers for the invitation, the audience for the patience and the interesting questions.
The code of the interpreter and compiler I've discussed is here: https://github.com/pcaressa/awful
-
Some pictures from my last talk at #Codemotion Milan Conference: thanks to the organizers for the invitation, the audience for the patience and the interesting questions.
The code of the interpreter and compiler I've discussed is here: https://github.com/pcaressa/awful