Exercism exercises in GNU APL.
Home Page: https://exercism.org/tracks/gnu-apl
License: MIT License
Quite a lot of work has been done to configure this track. There are 8 exercises.
If you wish to work on this track, please post in the Exercism Community Forum to discuss it with the team.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
The track's config.json file must have a non-empty blurb property. This property should contain a short description (less than or equal to 400 characters) of the language. See https://github.com/exercism/docs/blob/main/building/tracks/config-json.md.
We're going to need three things for the track landing page on the new Exercism site:
Location: ./config.json (field: "blurb").
The blurb will show up just under the header of the page. It will also be used on the overview page for all the tracks.
The aim of this is to give someone a really quick feel for what the language is about and why it might appeal to them. This should be a couple of sentences totaling ~30 words, in plain text (not markdown).
A couple of examples:
Go
Go is a compiled, open source programming language with a small, consistent syntax, a powerful standard library, and fantastic tooling. It's a great fit for web backends and command-line tools.
R
R is an interpreted, open source programming language with powerful data manipulation and graphical capabilities. It has a thriving package ecosystem and is one of the most popular languages for data science.
Location: docs/ABOUT.md.
This provides a bit more detail about the language. It might talk about its history, design goals, or about what the language is a great fit for, etc. This should be 70-120 words split over 1-3 paragraphs.
This text should be a friendly, genuine sales pitch for why someone should learn the language. It should not be an in-depth introduction, and it should not be a quote from another source, though it can certainly point people to other sources if they want to learn more.
It can be in markdown format, but should only contain links and emphasis (bold, italic).
Write each sentence on its own line, separate paragraphs with a blank line between them.
A couple of examples:
Location: the default is to use the reference solution to the first core exercise on the track. Override this by providing a docs/SNIPPET.txt file.
The code sample will appear in a small "frame" (image) on the right-hand side of the page, next to "About GNU APL".
This provides, at a glance, the style of the language. It needs to be 6-10 lines long and <=40 chars per line.
See exercism/discussions#173 for the original discussion about this with some questions/clarifications from other maintainers.
This issue is part of the migration to v3. You can read full details about the various changes here.
There are several new features in Exercism v3 for tracks to build. To selectively enable these features on the Exercism v3 website, each track must keep track of the status of the following features:
The status of these features is specified in the top-level "status" field in the track's config.json, as specified in the spec.
The "status" field in the config.json file should be updated to indicate the status of the features for this track. The list of features is defined in the spec.
{
"status": {
"concept_exercises": true,
"test_runner": true,
"representer": false,
"analyzer": false
}
}I'm the primary maintainer for this repo, but it looks like I don't have administrative permissions on it. Can we fix that?
Exercism uses highlightjs for syntax highlighting. Unfortunately, there is no support for this track at the moment (see the supported languages).
To properly support syntax highlighting for this track, an official grammar should be created at https://github.com/highlightjs/highlight.js/tree/main/src/languages. Note that this grammar could be relatively minimal at first and can be expanded upon at a later time.
@joshgoebel has initimate knowledge of the code base and has graciously offered to be available for any questions.
This issue is part of the migration to v3. You can read full details about the various changes here.
In Exercism v3, we're introducing a new (optional) tool: the representer. The goal of the representer is to take a solution and returning a representation, which is an extraction of a solution to its essence with normalized names, comments, spacing, etc. but still uniquely identifying the approach taken. Two different ways of solving the same exercise must not have the same representation.
Each representer is track-specific. When a new solution is submitted, we run the track's representer, which outputs two JSON files that describe the representation.
Once we have a normalized representation for a solution, a team of vetted mentors will look at the solution and comment on it (if needed). These comments will then automatically be submitted to each new solution with the same representation. A notification will be sent for old solutions with a matching representation.
Each track should build a representer according to the spec. For tracks building a representer from scratch, we have a starting guide.
The representer is an optional tool though, which means that if a track does not have a representer, it will still function normally.
In Exercism v3, we are making increased use of our v2 analyzers. Analyzers automatically assess student's submissions and provide mentor-style commentary. They can be used to catch common mistakes and/or do complex solution analysis that can't easily be done directly in a test suite.
Each analyzer is track-specific. When a new solution is submitted, we run the track's analyzer, which outputs a JSON file that contains the analysis results.
In v2, analyzer comments were given to a mentor to pass to a student. In v3, the analyzers will normally output directly to students, although we have added an extra key to output suggestions to mentors. If your track already has an analyzer, the only requisite change is updating the outputted copy to be student-facing.
Each track should build an analyzer according to the spec. For tracks building an analyzer from scratch, we have a starting guide.
The analyzer is an optional tool though, which means that if a track does not have an analyzer, it will still function normally.
Build a representer for your track according to the spec. Check this page to help you get started with building a representer.
Note that the simplest representer is one that merely returns the solution's source code.
It can be very useful to check how other tracks have implemented their representer.
Build an analyzer for your track according to the spec. Check this page to help you get started with building an analyzer.
It can be very useful to check how other tracks have implemented their analyzer.
If you want to build both, we recommend starting by building the representer for the following reasons:
Each track needs a file that contains track-specific instructions on how to manually run the tests. The contents of this document are only presented to the student when using the CLI. This file lives at exercises/shared/.docs/tests.md. You almost certainly already have this information, but need to move it to the correct place.
For v2 tracks, this information was (usually) included in the readme template found at config/exercise_readme.go.tmpl. As such, tracks can extract the test instructions from the config/exercise_readme.go.tmpl file to the exercises/shared/.docs/tests.md file.
See https://github.com/exercism/csharp/pull/1557/files for an example PR.
Each track needs a file that contains track-specific instructions on how to get help. The contents of this document are only presented to the student when using the CLI. This file lives at exercises/shared/.docs/help.md. You almost certainly already have this information, but need to move it to the correct place.
For v2 tracks, this information was (usually) included in the readme template found at config/exercise_readme.go.tmpl. As such, tracks can extract the help instructions from the config/exercise_readme.go.tmpl file to the exercises/shared/.docs/help.md file.
See https://github.com/exercism/csharp/pull/1557/files for an example PR.
Implement a track test suite that can run both locally and on Travis CI. The track test suite should verify that each exercise makes sense, by running the exercise tests against the example solution.
Definition of terms
Background
When implementing an exercise test suite, we want to provide a good user experience for the people writing a solution to the exercise. People should not be confused or overwhelmed.
In most Exercism language tracks, we simulate Test-Driven Development (TDD) by implementing the tests in order of increasing complexity. We try to ensure that each test either
Many test frameworks will randomize the order of the tests when running them. This is an excellent practice, which helps ensure that subsequent tests are not dependent on side effects from earlier tests. However, in order to simulate TDD we want tests to run in the order that they are defined, and we want them to fail fast, that is to say, as soon as the test suite encounters a failure, we want the execution to stop. This ensures that the person implementing the solution sees only one error or failure message at a time, unless they make a change which causes prior tests to fail.
This is the same experience that they would get if they were implementing each new test themselves.
Most testing frameworks do not have the necessary configuration options to get this behavior directly, but they often do have a way of marking tests as skipped or pending. The mechanism for this will vary from language to language and from test framework to test framework.
Whatever the mechanism—functions, methods, annotations, directives, commenting out tests, or some other approach—these are changes made directly to the test file. The person solving the exercise will need to edit the test file in order to "activate" each subsequent test.
Any tests that are marked as skipped will not be verified by the track test suite unless special care is taken.
Additionally, in some programming languages, the name of the file containing the solution is hard-coded in the test suite, and the example solution is not named in the way that we expect people to name their files.
We will need to temporarily (and programmatically) edit the exercise test suites to ensure that all of their tests are active. We may also need to rename the example solution file(s) in order for the exercise test suite to run against it.
Avoiding accidental git check-ins
It's important that if we rewrite files in any way during a test run, that these changes do not accidentally get checked in to the git repository.
Therefore, many language tracks write the track test suite in such a way that it copies the exercise to a temporary location outside of the git repository before editing or rewriting the exercise files during a test run.
Working around long-running track test suites
Usually as people are developing the track, they're focused on a single exercise. If running the entire track test suite against all of the exercises takes a long time, it is often worth making it possible to verify just one exercise at a time.
Example build file
The PHP track has created a Makefile. The Ruby track uses Rake, which is a tool written in Ruby, allowing the track maintainers to write custom code in the language of the track to customize the build with a Rakefile.
This issue is part of the migration to v3. You can read full details about the various changes here.
Exercism v3 introduces a new type of exercise: Concept Exercises. All existing (V2) exercises will become Practice Exercises.
Concept Exercises and Practice Exercises are linked to each other via Concepts. Concepts are taught by Concept Exercises and practiced in Practice Exercises. Each Exercise (Concept or Practice) has prerequisites, which must be met to unlock an Exercise - once all the prerequisite Concepts have been "taught" by a Concept Exercise, the exercise itself becomes unlocked.
For example, in some languages completing the Concept Exercises that teach the "String Interpolation" and "Optional Parameters" concepts might then unlock the two-fer Practice Exercise.
Each Practice Exercise has two fields containing concepts: a practices field and a prerequisites field.
The practices key should list the slugs of Concepts that this Practice Exercise actively allows a student to practice.
strings). In those cases we recommend choosing a few good exercises that make people think about those Concepts in interesting ways. For example, exercises that require UTF-8, string concatenation, char enumeration, etc, would all be good examples.The prerequisites key lists the Concept Exercises that a student must have completed in order to access this Practice Exercise.
strings, optional-params, implicit-return.loops or recursion), the maintainer should choose the one approach that they would like to unlock the Exercise, considering the student's journey through the track. For example, the loops/recursion example, they might think this exercise is a good early practice of loops or that they might like to leave it later to teach recursion. They can also make use of an analyzer to prompt the student to try an alternative approach: "Nice work on solving this via loops. You might also like to try solving this using Recursion."Although ideally all Concepts should be taught by Concept Exercises, we recognise that it will take time for tracks to achieve that. Any Practice Exercises that have prerequisites which are not taught by Concept Exercises, will become unlocked once the final Concept Exercise has been completed.
The "practices" field of each element in the "exercises.practice" field in the config.json file should be updated to contain the practice concepts. See the spec.
To help with identifying the practice concepts, the "topics" field can be used (if it has any contents). Once prerequisites have been defined for a Practice Exercise, the "topics" field should be removed.
Each practice concept should have its own entry in the top-level "concepts" array. See the spec.
The "prerequisites" field of each element in the "exercises.practice" field in the config.json file should be updated to contain the prerequisite concepts. See the spec.
To help with identifying the prerequisites, the "topics" field can be used (if it has any contents). Once prerequisites have been defined for a Practice Exercise, the "topics" field should be removed.
Each prerequisite concept should have its own entry in the top-level "concepts" array. See the spec.
{
"exercises": {
"practice": [
{
"uuid": "8ba15933-29a2-49b1-a9ce-70474bad3007",
"slug": "leap",
"name": "Leap",
"practices": ["if-statements", "numbers", "operator-precedence"],
"prerequisites": ["if-statements", "numbers"],
"difficulty": 1
}
]
}
}Hello 🙂
Over the last few months we've been transferring all our CI from Travis to GitHub Actions (GHA). We've found that GHA are easier to work with, more reliable, and much much faster.
Based on our success with GHA and increasing intermittent failures on Travis, we have now decided to try and remove Travis from Exercism's org altogether and shift everything to GHA. This issue acts as a call to action if your track is still using Travis.
For most CI checks this should be a transposing from Travis' syntax to GHA syntax, and hopefully quite straightforward (see this PR for an example). However, if you do encounter any issues doing this, please ask on Slack where lots of us now have experience with GHA, or post a comment here and I'll tag relevant people. This would also make a good Hacktoberfest issue for anyone interested in making their first contribution 🙂
If you've already switched this track to GHA, please feel free to close this issue and ignore it.
Thanks!
This issue is part of the migration to v3. You can read full details about the various changes here.
In Exercism v3, tracks can be annotated with tags. This allows searching for tracks with a certain tag combination, making it easy for students to find an interesting track to join.
Tags are specified in the top-level "tags" field in the track's config.json file and are defined as an array of strings, as specified in the spec.
The "tags" field in the config.json file should be updated to contain the tags that are relevant to this track. The list of tags that can be used is listed in the spec.
{
"tags": [
"runtime/jvm",
"platform/windows",
"platform/linux",
"paradigm/declarative",
"paradigm/functional",
"paradigm/object_oriented"
]
}Note: the launch checklist has been made obsolete by a brand new Launch Guide: https://github.com/exercism/docs/blob/master/language-tracks/launch/README.md
Let's keep the general discussions around what needs to be done here in this issue, and open new, actionable issues for next steps.
In Exercism v3, we are making increased use of our v2 analyzers. Analyzers automatically assess student's submissions and provide mentor-style commentary. They can be used to catch common mistakes and/or do complex solution analysis that can't easily be done directly in a test suite.
Each analyzer is track-specific. When a new solution is submitted, we run the track's analyzer, which outputs a JSON file that contains the analysis results.
In v2, analyzer comments were given to a mentor to pass to a student. In v3, the analyzers will normally output directly to students, although we have added an extra key to output suggestions to mentors. If your track already has an analyzer, the only requisite change is updating the outputted copy to be student-facing.
The analyzer is an optional tool though, which means that if a track does not have an analyzer, it will still function normally.
Build an analyzer for your track according to the spec. Check this page to help you get started with building an analyzer.
It can be very useful to check how other tracks have implemented their analyzer.
If your track already has a working analyzer, please close this issue and ensure that the .status.analyzer key in the track config.json file is set to true.
There is some overlap between the goals of the representer and the analyzer. If you want to build both, we recommend starting by building the representer for the following reasons:
We have decided to require all file-based tracks to provide stubs for their exercises.
The lack of stub file generates an unnecessary pain point within Exercism, contributing a significant proportion of support requests, making things more complex for our students, and hindering our ability to automatically run test-suites and provide automated analysis of solutions.
We believe that it’s essential to understand error messages, know how to use an IDE, and create files. However, getting this right as you’re just getting used to a language can be a frustrating distraction, as it can often require a lot of knowledge that tends to seep in over time. At the start, it can be challenging to google for all of these details: what file extension to use, what needs to be included, etc. Getting people up to speed with these things are not Exercism’s focus, and we’ve decided that we are better served by removing this source of confusion, letting people get on with actually solving the exercises.
The original discussion for this is at exercism/discussions#238.
Therefore, we’d like this track to provide a stub file for each exercise.
With all Exercism exercises I have with GNU/APL 1.7:
***** TEST LOG *****
VALENCE ERROR
test¯read_unicode[1] unicode←19 ⎕CR ⎕FIO[26]filename
^ ^
)SI not cleared at the end of hello-world.tc:
test¯read_unicode[1] unicode←19 ⎕CR ⎕FIO[26]filename
^ ^
test∆show_log[3] test¯warn test¯read_unicode filename
^
⋆ test∆show_log log
^This did not occur with GNU/APL 1.6.
The error is not a failing test case but appears to come directly from the unit test harness' show_log function.
There are a number of things we're going to want to check before the v2 site goes live. There are notes below that flesh out all the checklist items.
TODO)coreauto_approve: trueThe v2 site has a landing page for each track, which should make people want to join it. If the track page is missing, ping @kytrinyx to get it added.
If the header of the page starts with TODO, then submit a pull request to https://github.com/exercism/gnu-apl/blob/master/config.json with a blurb key. Remember to get configlet and run configlet fmt . from the root of the track before submitting.
If the "About" section feels a bit dry, then submit a pull request to https://github.com/exercism/gnu-apl/blob/master/docs/ABOUT.md with suggested tweaks.
In order to work well with the design of the new site, we're restricting the formatting of the ABOUT.md. It can use:
Additionally:
<br/> can be used to split a paragraph into lines without spacing between them, however this is discouraged.If the code example is too short or too wide or too long or too uninteresting, submit a pull request to https://github.com/exercism/ocaml/blob/master/docs/SNIPPET.txt with a suggested replacement.
Where the v1 site has a long, linear list of exercises, the v2 site has organized exercises into a small set of required exercises ("core").
If you update the track config, remember to get configlet and run configlet fmt . from the root of the track before submitting.
Core exercises unlock optional additional exercises, which can be filtered by topic an difficulty, however that will only work if we add topics and difficulties to the exercises in the track config, which is in https://github.com/exercism/gnu-apl/blob/master/config.json
We've currently made any hello-world exercises auto-approved in the backend of v2. This means that you don't need mentor approval in order to move forward when you've completed that exercise.
Not all tracks have a hello-world, and some tracks might want to auto approve other (or additional) exercises.
There are no bullet points for this one :)
As we move towards the launch of the new version of Exercism we are going to be ramping up on actively recruiting people to help provide feedback. Our goal is to get to 100%: everyone who submits a solution and wants feedback should get feedback. Good feedback.
If you're interested in helping mentor the track, check out http://mentoring.exercism.io/
When all of the boxes are ticked off, please close the issue.
Tracking progress in exercism/meta#104
This issue is part of the migration to v3. You can read full details about the various changes here.
In Exercism v3, students can now choose to work on exercises directly from their browser, instead of having to download exercises to their local machine. The track-specific settings for the in-browser editor are defined in the top-level "online_editor" field in the track's config.json file. This field is defined as an object with two fields:
"indent_style": the indent style, either "space" or "tab"."indent_size": the indent size, which is an integer (e.g. 4).You can find a full description of these fields in the spec.
The "online_editor" field should be updated to correspond to the track's best practices regarding indentation.
"online_editor": {
"indent_style": "space",
"indent_size": 4
}In line with our new org-wide policy, the master branch of this repo will be renamed to main. All open PRs will be automatically repointed.
GitHub will show you a notification about this when you look at this repo after renaming:
In case it doesn't, this is the command it suggests:
git branch -m master main
git fetch origin
git branch -u origin/main main
You may like to update the primary branch on your forks too, which you can do under Settings->Branches and clicking the pencil icon on the right-hand-side under Default Branch:
We will post a comment below when this is done. We expect it to happen within the next 12 hours.
See #6 (comment): we need to move config and library files around, probably by specifying a setup_files key.
We’ve recently started a project to find the best way to design our tracks, in order to optimize the learning experience of students.
As a first step, we’ll be examining the ways in which languages are unique and the ways in which they are similar. For this, we’d really like to use the knowledge of everyone involved in the Exercism community (students, mentors, maintainers) to answer the following questions:
Could you spare 5 minutes to help us by answering these questions? It would greatly help us improve the experience students have learning GNU APL :)
Note: this issue is not meant as a discussion, just as a place for people to post their own, personal experiences.
Want to keep your thoughts private but still help? Feel free to email me at [email protected]
Thank you!
This issue is part of the migration to v3. You can read full details about the various changes here.
In Exercism v3, each track must specify exactly six "key features". Exercism uses these features to highlight the most interesting, unique or "best" features of a language to a student.
Key features are specified in the top-level "key_features" field in the track's config.json file and are defined as an array of objects, as specified in the spec.
The "key_features" field in the config.json file should be updated to describe the six "key features" of this track. See the spec.
{
"key_features": [
{
"icon": "features-oop",
"title": "Modern",
"content": "C# is a modern, fast-evolving language."
},
{
"icon": "features-strongly-typed",
"title": "Cross-platform",
"content": "C# runs on almost any platform and chipset."
},
{
"icon": "features-functional",
"title": "Multi-paradigm",
"content": "C# is primarily an object-oriented language, but also has lots of functional features."
},
{
"icon": "features-lazy",
"title": "General purpose",
"content": "C# can be used for a wide variety of workloads, like websites, console applications, and even games."
},
{
"icon": "features-declarative",
"title": "Tooling",
"content": "C# has excellent tooling, with linting and advanced refactoring options built-in."
},
{
"icon": "features-generic",
"title": "Documentation",
"content": "Documentation is excellent and exhaustive, making it easy to get started with C#."
}
]
}As we move towards the launch of the new version of Exercism we are going to be ramping up on actively recruiting people to help provide feedback.
Our goal is to get to 100%: everyone who submits a solution and wants feedback should get feedback. Good feedback. You can read more about this aspect of the new site here: http://mentoring.exercism.io/
To do this, we're going to need a lot more information about where we can find language enthusiasts.
In other words: where do people care a lot and/or know a lot about GNU APL?
This is part of the project being tracked in exercism/meta#103
Some exercise README templates contain links to pages which no longer exist in v2 Exercism.
For example, C++'s README template had a link to /languages/cpp for instructions on running tests. The correct URLs to use can be found in the 'Still stuck?' sidebar of exercise pages on the live site. You'll need to join the track and go to the first exercise to see them.
Please update any broken links in the 'config/exercise_readme.go.tmpl' file, and run 'configlet generate .' to generate new exercise READMEs with the fixes.
Instructions for generating READMEs with configlet can be found at:
https://github.com/exercism/docs/blob/master/language-tracks/exercises/anatomy/readmes.md#generating-a-readme
Instructions for installing configlet can be found at:
https://github.com/exercism/docs/blob/bc29a1884da6c401de6f3f211d03aabe53894318/language-tracks/launch/first-exercise.md#the-configlet-tool
Tracking exercism/exercism#4102
We'll work with a designer to design an icon for the track.
In order to do so, we're going to need:
For some context and background and a look at how we've done this research for other languages, check out exercism/meta#24
Here's a screenshot of the icons for some of the tracks. This is for the new site (which is close to being launched) rather than the pink/black icons that you see on the old site. No designers were involved in those :)
Please check if your documentation files are still up-to-date.
The key documentation files to check are:
docs/ABOUT.mddocs/INSTALLATION.mddocs/LEARNING.mddocs/RESOURCES.mddocs/TESTS.mdexercises/shared/.docs/help.mdexercises/shared/.docs/tests.mdThere might be more.
To help identify invalid links, we've automatically checked the links of all *.md files in this repo.
This is the report of that check:
📝 Summary --------------------- 🔍 Total...........17 ✅ Successful......17 ⏳ Timeouts.........0 🔀 Redirected.......0 👻 Excluded.........0 🚫 Errors...........0
If you use a machine that is running the X-11 Window system then you are fortunate because an APL keyboard definition should already be installed. Check for /usr/share/X11/xkb/symbols/apl (or equivalent).
You should be able to configure the APL keyboard as an alternative keyboard layout. There are many desktops so the details differ. Navigate to:
System Setting → Hardware → Input Devices → Keyboard → Layouts
There click on the Add button of Configure Layouts. By rights, APL will be at the top of the alphabetic list that pop-ups.
You may want to set the 'switching policy' to Window and to choose shortcuts for switching layouts. Go to the 'Advanced' tab and expand the Keys(s) to change layout for a full list of available shortcuts .
A very effective choice is both Left Win (while pressed) and Right Win (while pressed). This allows you to enter APL symbols by modifier making use of two keys you may have never ever had any use for before.
If your desktop is too user friendly to offer you the APL keyboard you can edit a flat configuration file by hand and restart your X server instead.
On GNU/Linux Debian and derivatives, edit /etc/default/keyboard. Two lines will need to be changed to something similar to:
XKBLAYOUT="us,apl"
XKBOPTIONS="compose:menu,grp:lwin_switch,grp:rwin_switchI don't mean to tread on anyone's toes, take anyone out of their comfort zone or break any of Exercism's unwritten rules.
I am sorry to see that moving from GNU/APL 1.6 to 1.7 is giving problems. I wonder if it is time to consider another way.
I use different languages for different purposes. I try to play to their strengths. Usually trying to do something the language permits but was not designed for gives scope for regret.
Take running a GNU/APL test case. Currently I use:
apl -s -T *.tcI confess I don't find that easy to remember so I would wrap it up in a one line shell script (and then embellish later as my needs dictate).
OK. I use Linux and I don't think there is a version of Linux that does not have a shell (unless you count Android) and the same goes for MAC OS (unless you count iOS). I can't see anyone using GNU/APL on a mobile because mobiles don't have a command line (which I why they have no shell). Windows ? Well, the GNU/APL web site says you can compile it under cygwin for Windows so even there there is a shell. So I believe no one would have to install extra software just to run a one line script.
It appears to me that to run a test case, three files are concatenated together. That is what the ⎕FIO stuff is doing. The bare bones of a shell script that does this might look like:
echo "#!/usr/bin/env apl --script" > apl_test.tc
cat slug.apl test_harness.apl test_slug.apl >> apl_test.tcGNU/APl generates a log and currently ⎕FIO is used to print this out. That too could be replaced so a shell script that does the bare minimum might look like:
echo "#!/usr/bin/env apl --script" > slug.tc
cat slug.apl test_harness.apl test_slug.apl >> slug.tc
apl -s -T slug.tc
cat slug.tc.logAn added bonus is that folk attempting the exercise would not have to start their solution with "#!" line that clearly isn't APL (and isn't portable to other variants).
In Exercism v3, we're introducing a new (optional) tool: the representer. The goal of the representer is to take a solution and returning a representation, which is an extraction of a solution to its essence with normalized names, comments, spacing, etc. but still uniquely identifying the approach taken. Two different ways of solving the same exercise must not have the same representation.
Each representer is track-specific. When a new solution is submitted, we run the track's representer, which outputs two JSON files that describe the representation.
Once we have a normalized representation for a solution, a team of vetted mentors will look at the solution and comment on it (if needed). These comments will then automatically be submitted to each new solution with the same representation. A notification will be sent for old solutions with a matching representation.
The representer is an optional tool though, which means that if a track does not have a representer, it will still function normally.
Build a representer for your track according to the spec. Check this page to help you get started with building a representer.
Note that the simplest representer is one that merely returns the solution's source code.
It can be very useful to check how other tracks have implemented their representer.
If your track already has a working representer, please close this issue and ensure that the .status.representer key in the track config.json file is set to true.
There is some overlap between the goals of the representer and the analyzer. If you want to build both, we recommend starting by building the representer for the following reasons:
This repository's main branch currently does not pass all CI checks.
This makes detecting issues in PRs harder and might result in a broken track, and so is an important thing to fix.
The following CI workflows are currently failing:
https://github.com/exercism/gnu-apl/runs/3066721073
This issue is part of the migration to v3. You can read full details about the various changes here.
The configlet tool has a lint command that checks if a track's configuration files are properly structured - both syntactically and semantically. Misconfigured tracks may not sync correctly, may look wrong on the website, or may present a suboptimal user experience, so configlet's guards play an important part in maintaining the integrity of Exercism.
We're updating configlet to work with v3 tracks, which have a different set of requirements than v2 tracks.
The full list of rules that will be checked by the linter can be found in this spec.
⚠ Note that only a subset of the linting rules has been implemented at this moment. This means that while your track may be passing the checks at this moment, it might fail later. We thus strongly suggest you keep this issue open until we let you know otherwise.
Ensure that the track passes all the (v3 track) checks defined in configlet lint.
To help verify that the track passes all the linting rules, the v3 preparation PR has added a GitHub Actions workflow that automatically runs configlet lint.
It is also possible to run configlet lint locally by running the ./bin/fetch-configlet (or ./bin/fetch-configlet.ps1) script to download a local copy of the configlet binary. Once downloaded, you can then do ./bin/configlet lint to run the linting on your own machine.
Issue seen with GNU/APL 1.6 and GNU/APL 1.7.
I don't wish to point fingers. There is some confusion somewhere. More than happy for it to be my poor understand of advanced features.
For the 'hamming' exercise that are two test cases that expect the function under test to 'return' LENGTH ERROR when one operand is scalar-like and the other operand is not.
The function:
∇z←A distance B
⎕ES ((≢A) ≠ (≢B)) / 5 3
z ← +/ A ≠ B
∇gives the expected result when invoked directly from the interpreter but not when invoked from the test harness. This function:
∇z←A distance B
'HELLO ERROR' ⎕ES ((≢A) ≠ (≢B)) / 5 3
z ← +/ A ≠ B
∇works with the test harness - it sees the function as 'returning' LENGTH ERROR even though, when invoked directly from the APL interpreter, it is seen as 'returning' HELLO ERROR.
This issue is part of the migration to v3. You can read full details about the various changes here.
To get your track ready for Exercism v3, the following needs to be done:
This issue may be automatically added to over time. While track maintainers should check off completed items, please do not add/edit items in the list.
This issue is part of the migration to v3. You can read full details about the various changes here.
Concept Exercises can have a status specified in their "status" field in their config.json entry, as specified in the spec. This status can be one of four values:
"wip": A work-in-progress exercise not ready for public consumption. Exercises with this tag will not be shown to students on the UI or be used for unlocking logic. They may appear for maintainers."beta": This signifies active exercises that are new and which we would like feedback on. We show a beta label on the site for these exercise, with a Call To Action of "Please give us feedback.""active": The normal state of active exercises"deprecated": Exercises that are no longer shown to students who have not started them (not usable at this stage).The "status" key can also be omitted, which is the equivalent of setting it to "active".
The "status" field of Concept Exercises in the config.json file should be updated to reflect the status of the Concept Exercises. See the spec for more information.
If your track doesn't have any Concept Exercises, this issue can be closed.
{
"exercises": {
"concept": [
{
"uuid": "93fbc7cf-3a7e-4450-ad22-e30129c36bb9",
"slug": "cars-assemble",
"name": "Cars, Assemble!",
"concepts": ["if-statements", "numbers"],
"prerequisites": ["basics"]
},
...
]
}
}{
"exercises": {
"concept": [
{
"uuid": "93fbc7cf-3a7e-4450-ad22-e30129c36bb9",
"slug": "cars-assemble",
"name": "Cars, Assemble!",
"concepts": ["if-statements", "numbers"],
"prerequisites": ["basics"],
"status": "active"
},
...
]
}
}TL;DR; At the end of Jan 2021, all tracks will enter v3 staging mode. Updates will no longer sync with the current live website, but instead sync with the staging website. The GNU APL section of the v3 repo will be extracted and PR'd into this track (if appropriate). Further issues and information will follow over the coming weeks to prepare GNU APL for the launch of v3.
Over the last 12 months, we've all been hard at work developing Exercism v3. Up until this point, all v3 tracks have been under development in a single repository - the v3 repository. As we get close to launch, it is time for us to explode that monorepo back into the normal track repos. Therefore, at the end of this month (January 2021), we will copy the v3 tracks contents from the v3 repository back to the corresponding track repositories.
As v3 tracks are structured differently than v2 tracks, the current (v2) website cannot work with v3 tracks. To prevent the v2 website from breaking, we'll disable syncing between track repositories and the website. This will effectively put v2 in maintenance mode, where any changes in the track repos won't show up on the website. This will then allow tracks to work on preparing for the Exercism v3 launch.
Where possible, we will script the changes needed to prepare tracks for v3. For any manual changes that need to be happening, we will create issues on the corresponding track repositories. We will be providing lots of extra information about this in the coming weeks.
We're really excited to enter the next phase of building Exercism v3, and to finally get it launched! 🙂
Some tracks have added assertions to the exercise test suites that ensure that the solution has a hard-coded version in it.
In the old version of the site, this was useful, as it let commenters see what version of the test suite the code had been written against, and they wouldn't accidentally tell people that their code was wrong, when really the world had just moved on since it was submitted.
If this track does not have any assertions that track versions in the exercise tests, please close this issue.
If this track does have this bookkeeping code, then please remove it from all the exercises.
See exercism/exercism#4266 for the full explanation of this change.
This issue is part of the migration to v3. You can read full details about the various changes here.
In Exercism v3, one of the biggest changes is that we'll automatically check if a submitted solution passes all the tests.
We'll check this via a new, track-specific tool: the Test Runner. Each test runner is track-specific. When a new solution is submitted, we run the track's test runner, which outputs a JSON file that describes the test results.
The test runner must be able to run the tests suites of both Concept Exercises and Practice Exercises. Depending on the test runner implementation, this could mean having to update the Practice Exercises to the format expected by the test runner.
Build a test runner for your track according to the spec.
If you are building a test runner from scratch, we have a starting guide and a generic test runner that can be used as the base for the new test runner.
If a test runner has already been built for this track, please check if it works on both Concept Exercises and Practice Exercises.
It can be very useful to check how other tracks have implemented their test runner.
Note that this is about the exercises (the test suites and code examples), not people's solutions.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.