PathElement

data class PathElement(type: Reflection.PathElementType, name: String, doEval: Boolean, params: List<Any?>)

Functions

component1

operator fun component1(): Reflection.PathElementType

component2

operator fun component2(): String

component3

operator fun component3(): Boolean

component4

operator fun component4(): List<Any?>

copy

fun copy(type: Reflection.PathElementType, name: String, doEval: Boolean = false, params: List<Any?> = listOf()): Reflection.PathElement

equals

open operator override fun equals(other: Any?): Boolean

hashCode

open override fun hashCode(): Int

toString

open override fun toString(): String

Properties

doEval

val doEval: Boolean = false

For key and index accesses, and function calls, whether to evaluate name instead of using params for arguments/key. This lets simple parsers be written and used, that can simply break up a common subset of many programming languages into string components without themselves having to analyze or understand any more complex semantics.

name

val name: String

params

val params: List<Any?>

type

val type: Reflection.PathElementType

Sources

jvm source