@thestuckster If you fork, conflicts in the description should be highlighted.
@SpecialEd https://www.scala-lang.org/documentation/learn.html Try the Coursera courses then maybe the first 1 or 2 books if you feel like.

List lengths should be checked too. Or even better you can use Scalatest matchers to compare entire lists in one assertion with better error messages.

Give me some good resources on Scala learning ... I am thinking of making a Visual python Gui builder with .net Controls and not IronPython... would this be a good idea for people, or just a pet project for my lonesome?

https://github.com/Codewars/codewars.com/issues/1359

;-)

Looks like a CW bug and not a kata bug. I'll report it to the github repo.

Removed

No.

Fixed

Fixed

The Scala version of this kata hasn't been implemented...

I think the type for n in fibTail should be Int:

def fibTail(n: Int, previous: Long, current: Long): Long = {...}

I don't see the reason why it should be of type Long:

def fibTail(n: Long, previous: Long, current: Long): Long = {...}

Since the original interface uses Int for n, and values are always decreasing, there is no point in using Long for the fibTail() method.

Thoughts?

hmmmm still get the same message. I will ask around. At the mean time hope someone can answer this.
Thanks for the contribution!

I'm not entirely sure to be honest. This is the first time I've written anything for codewars. I republished it again so maybe it will work this time?

Hey, I was trying to approve your tranlation but I get a warning saying that I need to merge previous change. This is the only kata I have ever written (year ago when I was new to coding) so I don't really know the whole lot about writing, approving kata process.
Where do I merge preious change?

Hey guys, I wrote a scala translation for this. Can you please go give it a look?

(I'm still a codewars green horn so I hope this link works)
https://www.codewars.com/kumite/5a85f8674a6b34fcb30009b0?sel=5a85f8674a6b34fcb30009b0