Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6216231
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T07:11:53+00:00 2026-05-24T07:11:53+00:00

Consider these two classes and the way the instances are created: class Person1(val name:

  • 0

Consider these two classes and the way the instances are created:

class Person1(val name: String)

val p1 = new Person1("John");

and:

abstract class Person2 {
  val name: String
}

val p2 = new Person2 {
  val name = "John"
}

Why would one prefer the latter (Person2) version? Every such a declaration causes new subclass to be created, also the code is slightly more verbose and less readable, however the second idiom is used throughout the Programming in Scala book several times. What are the advantages over straightforward field?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T07:11:56+00:00Added an answer on May 24, 2026 at 7:11 am

    One simple use case is with traits, which cannot have constructor arguments.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Consider these two classes: public class A { B b; public A(B b) {
Consider these two abstract classes. MyClass2 extends my BaseClass and overrides a virtual method.
Consider these two classes mapped to the same table. One is readonly via mutable=false.
Consider these classes. class Base { ... }; class Derived : public Base {
To give an idea of my requirement, consider these classes - class A {
Scenario 1: I have two classes: Post : class Post { String content Date
Consider these two function definitions: void foo() { } void foo(void) { } Is
I ran across a compilation issue today that baffled me. Consider these two container
What is the correct way of iterating over a vector in C++? Consider these
Consider, I have the following 3 classes / interfaces: class MyClass<T> { } interface

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.