Introduce consistent naming for scheme interface functions

[lukasdreyer]

Feature request

Consistent naming for scheme interface functions

Is your feature request related to a problem? Please describe.
Some functions are called get_, set_to_, construct with similar ideas.

Describe the solution or feature you'd like
From mattermost discussion:
get - if information on the current element is returned but the element is not changed (one const input)
set - if something is changed for the Input element (one input = output)
construct - if a new element is build from information of the input element (one const input, one non-const input = output)

Estimated priority
Which of these is most applicable (remove the others):

"Priority: low" Should be solved eventually

[lukasdreyer]

Answer from @holke from mattermost:

get - if information on the current element is returned but the element is not changed (one const input)
set - if something is changed for the Input element (one input = output)
construct - if a new element is build from information of the input element (one const input, one non-const input = output)