Project

General

Profile

Actions
Copy link

Feature #6627

open

Use common way to implement nondetermined behaviour

Added by Evgeny Novikov almost 9 years ago. Updated over 7 years ago.

Status:
New
Priority:
High
Assignee:
Evgeny Novikov
Category:
Requirement specifications
Target version:
-
Start date:
01/29/2016
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

The most proper solution is to have some common interface for modelling nondeterminism.

Actions
Copy link
 #1

Updated by Evgeny Novikov about 8 years ago

  • Assignee set to Evgeny Novikov
  • Priority changed from Normal to Immediate

This should be done together with other improvements in rule specifications.

Actions
Copy link
 #2

Updated by Evgeny Novikov almost 8 years ago

  • Priority changed from Immediate to Urgent

No progress during 4 months - this issue was incorrectly marked as immediate.

Actions
Copy link
 #3

Updated by Evgeny Novikov over 7 years ago

  • Priority changed from Urgent to High

I will do this but very slowly. So let's don't put this issue together with really important issues to be fixed/implemented quickly.

Actions
Copy link

Also available in: Atom PDF