This lesson is a lot of fun.
We’ll integrate what we’ve learned recently about String
s, algorithms, and then functions.
And then we’ll get some practice approaching a few new problems using String
s.
But let’s start with some debugging practice!
But first, we have a few new things to cover.
When we started working with variables and Kotlin’s eight basic types, we observed that there were certain types of assignments that would fail. For example:
Unlike some other languages, Kotlin will not automatically convert a value even if you might think it could be done safely:
So let’s look at how we can force Kotlin to perform certain type changes when necessary.
String
s Are ImmutableString
s Are ImmutableOne of the important things to understand about Kotlin’s String
s is that none of the methods that we can call on them change that String
.
Instead, they always return a new String
that may be modified in some way.
Let’s see that in action:
Array<>
and arrayOf
Array<>
and arrayOf
We’ll be working with arrays of String
s in this lesson.
Given that previously, when we used an array of Int
s we declared it as
IntArray
and initialized it using intArrayOf
, and when we used an array of Double
s we declared it as
DoubleArray
and initialized it using doubleArrayOf
, you might assume that an array of String
s would be
a StringArray
and intialized using stringArrayOf
:
But not quite! Instead, the actual syntax is a bit different:
On the left we see the type Array<String>
, which indicates that this is an
array that contains Strings
.
The type of the contents of the array is inside the angle brackets: <String>
.
On the right we see the generic array initializer for Kotlin, which you can use
to create arrays of any type.
As usual, we don’t need to specify the type explicitly on the left:
How does Kotlin know what type of array it is?
Based on the arguments to arrayOf
!
Since they are all String
s, the type is inferred as Array<String>
.
For now we’ll work with these arrays without worrying too much about what’s
going on under the hood.
Just be careful with arrayOf
, since if you mix the types of the arguments
things won’t work out as expected:
String
AlgorithmsString
AlgorithmsNow let’s have some fun and write a few new algorithms that work on String
s!
String
Character SearchString
Character SearchFirst, let’s try and write a function that determines if a String
contains a particular character.
We’ll sketch our our algorithm first, explore some potentially useful String
methods, and construct and test a solution.
String
ParsingString
ParsingFrequently when computers work with text data, we are processing data that was itself created by a machine. Or set up for machines to easily process.
One example is data stored in comma-separated-value format.
Let’s say we wanted to track how many people were tested for some random respiratory illness each day.
We might save that data in a String
that looked like this:
(Note that this is not real data!)
Let’s experiment with how we might work with this kind of data.
We’ll use some existing String
methods and a few new ones.
We’ll also use another unfamiliar method: String.toInt
, which allows us to convert a String
to an Int
.
Joy Buolamwini is a self-described poet of code who, through her art, voice, and research, is drawing attention to important social implications of the widespread use of artificial intelligence. Watch her speak for herself, in words both beautiful and powerful:
If you have a few more minutes, watch her TED Talk on algorithmic bias—what she calls “the coded gaze”.
Need more practice? Head over to the practice page.