Skip to content

mdsrosa/project_euler

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Project Euler's Solutions

Solutions for problems from projecteuler.net.

Solutions

NIY = Not Implemented Yet

Problem Python Ruby C Go Clojure Perl C++ Javascript Elixir
#001 Solution Solution Solution Solution Solution Solution Solution Solution Solution
#002 Solution Solution Solution Solution NIY Solution Solution Solution Solution
#003 Solution Solution Solution Solution NIY NIY NIY NIY NIY
#004 Solution Solution Solution Solution NIY NIY NIY NIY NIY
#005 Solution Solution Solution Solution NIY NIY NIY NIY NIY
#006 Solution Solution Solution Solution NIY NIY NIY NIY NIY
#007 Solution Solution Solution Solution NIY NIY NIY NIY NIY
#008 Solution Solution Solution Solution NIY NIY NIY NIY NIY
#009 Solution Solution Solution Solution NIY NIY NIY NIY NIY
#010 Solution Solution Solution Solution NIY NIY NIY NIY NIY

Contributing with your solution

Structure

Your solution file must be called solution and must be under solutions/problem_[problem number]/. If you need to create a utils file put it under utils/[language].

Commit messages

We use the following standard commit message:

Add [LANGUAGE] solution for problem [PROBLEM NUMBER]

If you implemented a solution using a another language, then the commit message should be: Add [LANGUAGE] implementation of [THE OTHER LANGUAGE] solution for problem [PROBLEM NUMBER]

LANGUAGE = The programming language you used to implement the solution.

PROBLEM NUMBER = The number of the problem that you solved.

Output format

The standard output for every implementation should be:

Time should be in seconds.

  => Result: 00000
  => Time: 0.0000s

In case of multiples solutions:

  => Solution 1
  => Result: 00000
  => Time: 0.0000s
  => Solution 2
  => Result: 00000
  => Time: 0.0000s
  ...

Pushing to the Github repository

  1. Fork it (https://github.com/mdsrosa/project_euler/fork)
  2. Create your solution branch git checkout -b username/add-[LANGUAGE]-solution-problem-[PROBLEM NUMBER]
  3. Commit your changes git commit -am 'Add [LANGUAGE] solution for problem [PROBLEM NUMBER]'
  4. Push to the branch git push origin username/add-[LANGUAGE]-solution-problem-[PROBLEM NUMBER]
  5. Create a new Pull Request

License

See the LICENSE file for license rights and limitations (MIT).