Make label a required argument

[loostrum]

Now the label argument is a keyword argument with a default of either 0 or 1, depending on the method.
Doesn't it make more sense to always ask the user which class they want an explanation for instead of assuming one?

[egpbos]

Sounds reasonable to me.

I'm thinking that refactoring the classes into more specific ones that also mention what task they do, so e.g. LimeImageClassifier ([name][modality][task]) as mentioned in #91 (comment), would also support this way of working. It should immediately be clear from the name Classifier that a class to explain must be provided. Similarly, for possible other tasks in the future, other arguments may be clear (e.g. a distance metric when you want to explain distance).

[cwmeijer]

See PR #426.