Named arguments for clarity in Kotlin - Mini Project: Build & Apply

Named arguments for clarity

📖 Scenario: You are creating a simple program to calculate the price of a product after applying a discount and adding tax. To make your code clear and easy to read, you will use named arguments when calling functions.

🎯 Goal: Build a Kotlin program that defines a function to calculate the final price of a product using named arguments for clarity. You will create the data, set up a discount rate, use named arguments in the function call, and print the final price.

📋 What You'll Learn

Create a function called calculateFinalPrice with parameters price, discount, and tax.

Use named arguments when calling calculateFinalPrice.

Print the final price with two decimal places.

💡 Why This Matters

🌍 Real World

Using named arguments helps programmers read and understand code easily, especially when functions have many parameters.

💼 Career

Clear code with named arguments is valued in software development jobs because it reduces mistakes and improves teamwork.

1

Create the product price variable

Create a variable called productPrice and set it to 100.0.

Kotlin

# Create a variable called productPrice and set it to 100.0
# Your code here

Hint

Use val productPrice = 100.0 to create the variable.

2

Set the discount rate

Create a variable called discountRate and set it to 0.15 (which means 15%).

Kotlin

val productPrice = 100.0
# Create a variable called discountRate and set it to 0.15
# Your code here

Hint

Use val discountRate = 0.15 to create the discount rate variable.

3

Define the function and use named arguments

Define a function called calculateFinalPrice that takes three Double parameters: price, discount, and tax. It should return the final price after applying the discount and adding tax. Then, create a variable called finalPrice and call calculateFinalPrice using named arguments: price = productPrice, tax = 0.08, and discount = discountRate.

Kotlin

val productPrice = 100.0
val discountRate = 0.15
# Define the function calculateFinalPrice and call it with named arguments
# Your code here

Hint

Define the function with the three parameters and return the final price. Use named arguments in the function call for clarity.

4

Print the final price

Print the value of finalPrice rounded to two decimal places using println. Use "%.2f".format(finalPrice) to format the output.

Kotlin

val productPrice = 100.0
val discountRate = 0.15

fun calculateFinalPrice(price: Double, discount: Double, tax: Double): Double {
    val discountedPrice = price * (1 - discount)
    return discountedPrice * (1 + tax)
}

val finalPrice = calculateFinalPrice(price = productPrice, tax = 0.08, discount = discountRate)
# Print the finalPrice rounded to two decimal places
# Your code here

Hint

Use println("Final price: $" + "%.2f".format(finalPrice)) to print the formatted price.

Practice

1. What is the main benefit of using named arguments in Kotlin functions?

easy

A. They make it clear which value is assigned to which parameter.

B. They automatically optimize the function's performance.

C. They allow functions to run without parameters.

D. They convert all arguments to strings.

Solution

1. Step 1: Understand named arguments purpose

   Named arguments explicitly show which value goes to which parameter, improving code readability.

2. Step 2: Compare with other options

   Options A, C, and D describe unrelated or incorrect effects of named arguments.

3. Final Answer:

   They make it clear which value is assigned to which parameter. -> Option A

4. Quick Check:

   Named arguments clarify parameter assignment = B [OK]

Hint: Named arguments clarify parameter names and values [OK]

Common Mistakes:

• Thinking named arguments improve performance
• Believing named arguments remove the need for parameters
• Confusing named arguments with type conversion

2. Which of the following is the correct way to call the function fun greet(name: String, age: Int) using named arguments?

easy

A. greet(age = 25, "Anna")

B. greet(name = "Anna", 25)

C. greet(name = "Anna", age = 25)

D. greet(name: "Anna", age: 25)

Solution

1. Step 1: Check named argument syntax

   Named arguments use parameter = value syntax, so greet(name = "Anna", age = 25) is correct.

2. Step 2: Identify incorrect options

   greet(name = "Anna", 25) mixes positional and named incorrectly; C has wrong order without naming first argument; D uses colon instead of equals.

3. Final Answer:

   greet(name = "Anna", age = 25) -> Option C

4. Quick Check:

   Named argument syntax uses = not : = A [OK]

Hint: Use parameter = value format for named arguments [OK]

Common Mistakes:

• Using colon (:) instead of equals (=) in named arguments
• Mixing positional and named arguments incorrectly
• Passing arguments in wrong order without naming

3. What will be the output of the following Kotlin code?

fun describePerson(name: String, age: Int = 30) {
    println("Name: $name, Age: $age")
}

describePerson(age = 22, name = "John")

medium

A. Name: John, Age: 30

B. Name: John, Age: 22

C. Name: 22, Age: John

D. Compilation error

Solution

1. Step 1: Analyze named arguments order

   Named arguments allow changing order, so age = 22 and name = "John" correctly assign values.

2. Step 2: Check default parameter usage

   Since age is provided, default 30 is ignored. Output prints name and age as given.

3. Final Answer:

   Name: John, Age: 22 -> Option B

4. Quick Check:

   Named arguments reorder parameters correctly = C [OK]

Hint: Named arguments let you reorder parameters safely [OK]

Common Mistakes:

• Assuming order must match function definition
• Ignoring default parameter when argument is provided
• Expecting compilation error due to argument order

4. Identify the error in the following Kotlin function call:

fun calculate(x: Int, y: Int = 10) = x + y

calculate(y = 5, 3)

medium

A. Function call is correct

B. Missing argument for parameter x

C. Default parameter cannot be overridden

D. Cannot use named argument before positional argument

Solution

1. Step 1: Check argument order rules

   In Kotlin, positional arguments must come before named arguments. Here, named argument y=5 comes before positional 3, which is invalid.

2. Step 2: Confirm error type

   This causes a syntax error because named arguments cannot precede positional ones.

3. Final Answer:

   Cannot use named argument before positional argument -> Option D

4. Quick Check:

   Named arguments must follow positional arguments = D [OK]

Hint: Positional args first, then named args [OK]

Common Mistakes:

• Placing named arguments before positional arguments
• Assuming default parameters can't be overridden
• Ignoring Kotlin's argument order rules

5. Given the function fun bookTicket(name: String, seat: String = "Standard", meal: String = "None"), which call correctly books a ticket for "Alice" with a "VIP" seat and default meal using named arguments?

hard

A. bookTicket(name = "Alice", seat = "VIP")

B. bookTicket("Alice", "VIP", meal = "None")

C. bookTicket(seat = "VIP", "Alice")

D. bookTicket(name = "Alice", meal = "None")

Solution

1. Step 1: Identify parameters to set

   We want to set name = "Alice" and seat = "VIP", but keep meal default.

2. Step 2: Check each option

   bookTicket(name = "Alice", seat = "VIP") sets name and seat with named arguments, skipping meal (default used). bookTicket("Alice", "VIP", meal = "None") mixes positional and named but explicitly sets meal to "None" (same as default). bookTicket(seat = "VIP", "Alice") uses named argument before positional argument, invalid. bookTicket(name = "Alice", meal = "None") sets meal explicitly but not seat.

3. Step 3: Choose best clarity and correctness

   bookTicket(name = "Alice", seat = "VIP") clearly sets only needed parameters with named arguments, using default meal.

4. Final Answer:

   bookTicket(name = "Alice", seat = "VIP") -> Option A

5. Quick Check:

   Named args set needed params, skip defaults = A [OK]

Hint: Name only needed params, skip defaults with named args [OK]

Common Mistakes:

• Setting default parameters explicitly when not needed
• Mixing positional and named arguments unnecessarily
• Changing argument order without naming