mycar | Your first self driving car project | Machine Learning library

Maybe the response you are getting is inconsistent. Some datas are int, some are string. So the best way to not get this error is to use dynamic.

Just use dynamic kilometer in your MyCar class. Also, remove as int

You can try this:

In the first snippet, myCar refers to the class car, and method1 appears to be being used as a static method of that class.

In the second snippet, myCar refers to an instance of the class car, and method1 is an instance method -- the typical usage. Instance methods receive as a first argument the instance calling the method.

Conceptually, the difference is that in the second snippet you're referring to a car and in the first snippet you're referring to the concept of cars in general.

Like you mentioned, Go has no inheritance in the typical sense. Embedding is really just syntactic sugar.

When embedding, you add a field to you struct with the exact same name as the type you are embedding. Any methods of the embedded struct can be called on the struct which embeds them, this does nothing more than forwarding them.

One tick is that, if the struct which embeds another already declares a method, it will be preferred over forwarding it, which allows you to sort of overwrite functions if you want to think of it like that.

As you have noticed, we can't use Car as a Vehicle even if Car embeds Vehicle since they are strictly not the same type. But any struct which embeds Vehicle will have all methods which were defined by Vehicle, thus if we define an interface which Vehicle implements, all types that embed Vehicle should also implement that interface.

For example:

Your carName typing is incorrect. Your code fixed:

Please check the code below.

That's right. The superclass can't use the shortcut notation of VEHICLE_TYPE to access the constant you've defined.

When you want to access a constant outside of the class it is defined in, you can access it using a qualified name like:

When you sort, you sort by the make and model, which is cool. But when you try and search, you set the make to "", so the result of comparing the entities won't work correctly.

You could modify the sort Comparator so as to ignore makes with "" when comparing them (so only using models) or supply the make as part of your search or create a seperate "search" Comparator, for example

Your program has many errors, you should read the warnings after loading the file into prolog.

1. Why are you using ; in the second clause of hasproperty predicate?
2. You spelled Object as Ojbect in the last two clauses.
3. Why are you asserting property(Property, Ojbect, _) in the last two clause at all?
4. Unless you have a very good reason, you should define all clauses of a predicate in one place. Do not intersperse rel and property like that. And if you have a good reason to do it, you must use discontiguous to declare them as such.

Prolog should have warned you about 2 and 4.