Exercism Julia Track

Exercism exercises in Julia.

Contributing Guide

Please see the contributing guide.

Please read and adhere to the Code of Conduct.

Code Formatting Guidelines

Your example solutions should adhere to the following guidelines:

4 spaces per indentation level, no tabs
use whitespace to make the code more readable
no whitespace at the end of a line (trailing whitespace)
comments are good, especially when they explain the algorithm
use upper camel case convention for type names
use lower case for method names, add underscores if necessary

These are based on the General Formatting Guidelines for contributions to the Julia codebase.

Exercise Formatting Guidelines

stub.jl

The solution file stub.jl takes the exercise name by default, in kebab case if necessary (e.g. exercise-name.jl).

The content of concept exercise stubs have function skeletons by default, (some of) which can be omitted if the exercise emphasizes manual coding of new concepts.
The content of practice exercise stubs is left to the discretion of the author.

When function skeletons are provided, they should include a blank new line with a four space indentation for the body.

function fun1(arg1)

end

function fun2(arg2, arg3)
    
end

runtests.jl

Every runtests.jl file should have the following skeleton:

using Test

include("stub.jl")

@testset verbose = true "tests" begin
    
    # Exercise specific testing: @testset / @test

end

Where the "tests" testset is a verbose wrapper for non-verbose exercise specific testing (used for formatting testing output). In other words, all (exercise specific) inner testset should omit verbose = true (e.g. first line: @testset "testset name" begin).

If helper files are needed for testing or boilerplate, place them in the same top-level folder as runtests.jl and explicitly include them in runtests.jl:

using Test

include("stub.jl")
include("testtools.jl")
include("boilerplate.jl")

@testset verbose = true "tests" begin
    
    # Exercise specific testing: @testset / @test

end

Note: Students will not need to import/include any boilerplate for use in stub.jl, but this can be encouraged for instructional purposes if desired. Likewise, .meta/example.jl or .meta/exemplar.jl does not need to import/include any boilerplate.

config.json

If helper files are needed, .meta/config.json should then take an entry under the "files" property.

If the file is meant to be visible to the student (e.g. Alphametics), use editor:

  "files": {
    "solution": [
      "stub.jl"
    ],
    "test": [
      "runtests.jl"
    ],
    "example": [
      ".meta/example.jl"
    ],
    "editor": [
      "boilerplate.jl"
    ]
  },

If the file is not meant to be visible to the student (e.g. Cater Waiter), use auxiliary:

  "files": {
    "solution": [
      "stub.jl"
    ],
    "test": [
      "runtests.jl"
    ],
    "example": [
      ".meta/example.jl"
    ],
    "auxiliary": [
      "testtools.jl"
    ]
  },

License

depial/julia

ErrorLooks like something went wrong!

About

Resources

License

Code of conduct

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages