Avatar of PatrickWalker

PatrickWalker's solution

to Acronym in the Go Track

Published at Jul 13 2018 · 0 comments
Instructions
Test suite
Solution

Note:

This solution was written on an old version of Exercism. The tests below might not correspond to the solution code, and the exercise may have changed since this code was written.

Convert a phrase to its acronym.

Techies love their TLA (Three Letter Acronyms)!

Help generate some jargon by writing a program that converts a long name like Portable Network Graphics to its acronym (PNG).

Running the tests

To run the tests run the command go test from within the exercise directory.

If the test suite contains benchmarks, you can run these with the --bench and --benchmem flags:

go test -v --bench . --benchmem

Keep in mind that each reviewer will run benchmarks on a different machine, with different specs, so the results from these benchmark tests may vary.

Further information

For more detailed information about the Go track, including how to get help if you're having trouble, please visit the exercism.io Go language page.

Source

Julien Vanier https://github.com/monkbroc

Submitting Incomplete Solutions

It's possible to submit an incomplete solution so you can see how others have completed the exercise.

acronym_test.go

package acronym

import (
	"testing"
)

func TestAcronym(t *testing.T) {
	for _, test := range stringTestCases {
		actual := Abbreviate(test.input)
		if actual != test.expected {
			t.Errorf("Acronym test [%s], expected [%s], actual [%s]", test.input, test.expected, actual)
		}
	}
}

func BenchmarkAcronym(b *testing.B) {
	for i := 0; i < b.N; i++ {
		for _, test := range stringTestCases {
			Abbreviate(test.input)
		}
	}
}

cases_test.go

package acronym

// Source: exercism/problem-specifications
// Commit: 5ae1dba Acronym canonical-data: Remove redundant test case
// Problem Specifications Version: 1.3.0

type acronymTest struct {
	input    string
	expected string
}

var stringTestCases = []acronymTest{
	{
		input:    "Portable Network Graphics",
		expected: "PNG",
	},
	{
		input:    "Ruby on Rails",
		expected: "ROR",
	},
	{
		input:    "First In, First Out",
		expected: "FIFO",
	},
	{
		input:    "GNU Image Manipulation Program",
		expected: "GIMP",
	},
	{
		input:    "Complementary metal-oxide semiconductor",
		expected: "CMOS",
	},
}
package acronym

import (
	"strings"
    "unicode"
)

const testVersion = 1

func abbreviate(in string) string {
	acr := ""
	splitString := strings.Fields(in)

	for _, entry := range splitString {
		//we will call a function here   
		acr = acr + parse(entry)
	}
    
	return strings.ToUpper(acr)
}


//split by - 

//first character is in

//Camel case is interesting because PHP is the trip up. If we take first letter off H will show up

//camel case split is not something to worry about yet so do the - split first. If more than 1 then we're good just take the first character

//if it's one then we want to take the first character and then the next camel case word. If it's lower case just take it then move on

func parse(input string) string {
    //taking first letter via a slice gets us part of the way
    res := ""
    //split by a - character iterate over values add first chars of those and return
     dashSplit := strings.Split(input, "-")
     
     if len(dashSplit) > 1 {
          for _, dash := range dashSplit  {
              res = res + dash[0:1]
          }
     } else{
        tok := dashSplit[0]
        if(unicode.IsUpper( []rune(tok)[0] )){
            //split on camel case
            capsArr := ParseCamelCase(tok)
            //get array elements and start building string
            for _, caps := range capsArr{                
                res = res + caps[0:1]
            }
        } else {
            res = res + tok[0:1]
        }
        
     }

    return res
}

func ParseCamelCase(input string) ([]string) {
    f := func(c rune) bool {
        return (unicode.IsLower(c) || !unicode.IsLetter(c))
    }
   return  strings.FieldsFunc(input, f)
    
}

Community comments

Find this solution interesting? Ask the author a question to learn more.

What can you learn from this solution?

A huge amount can be learned from reading other people’s code. This is why we wanted to give exercism users the option of making their solutions public.

Here are some questions to help you reflect on this solution and learn the most from it.

  • What compromises have been made?
  • Are there new concepts here that you could read more about to improve your understanding?