urdt/ussd
5
0
Fork 1
Code Issues 41 Pull Requests Actions Packages Projects Releases Wiki Activity

Minimize non-INCMP instructions after HALT #144

New Issue
Closed
opened 2024-10-28 18:51:46 +01:00 by lash · 1 comment
lash commented 2024-10-28 18:51:46 +01:00
Owner
Copy Link

go-vise was designed with the intention that instructions after a HALT in a menu node should only contain INCMP statement. At the complexity code of more node, it should reduce the complexity needed in external function execution, aswell as making debugging context more compartmentalized.

Whereas this is just an assumption, it would be worthwhile to test that assumption by:

  • Asserting the consequences of refactoring some existing code using other instructions after HALT to see the effect on the code.
  • Write future code according to this rule, to evaluate the resulting difficulty and complexity
go-vise was designed with the intention that instructions after a HALT in a menu node should only contain INCMP statement. At the complexity code of more node, it should reduce the complexity needed in external function execution, aswell as making debugging context more compartmentalized. Whereas this is just an assumption, it would be worthwhile to test that assumption by: - Asserting the consequences of refactoring some existing code using other instructions after HALT to see the effect on the code. - Write future code according to this rule, to evaluate the resulting difficulty and complexity
lash added the
Status
Need More Info
Activity
Proposal
 labels 2024-10-28 18:51:55 +01:00
lash added the
refactor
 label 2024-10-28 18:54:16 +01:00
lash changed title from Remove non-INCMP instructions after HALT to Minimize non-INCMP instructions after HALT 2024-10-31 00:07:53 +01:00
lash added
optimization
Activity
Doing
 and removed
Status
Need More Info
Activity
Proposal
 labels 2024-12-31 10:20:05 +01:00
carlos was assigned by lash 2024-12-31 10:20:17 +01:00
lash commented 2025-01-13 11:52:12 +01:00
Author
Owner
Copy Link

badly formulated issue, needs to be more concrete.

badly formulated issue, needs to be more concrete.
lash closed this issue 2025-01-13 11:52:12 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Activity
Doing
An item actively being worked on currently

  
Activity
Hold
Not being actively worked on

  
Activity
Proposal
A proposal for a new feature or enhancement

  
Activity
QA
Ready for QA testing

  
Activity
Validate
Dev team validating changes

  
Runner
AT

  
Runner
CLI

  
Runner
HTTP

  
Runner
SSH

  
cleanup

   
devops

   
documentation

   
easypeasy

A task that can be completed with little effort

  
exchange

relating to swapping of assets and offramps

  
i18n

Languages and translations

  
legacy

Legacy features from the old ussd system to be ported

  
meta

container for other issues

  
migration

   
optimization

   
privilege

features that have to do with special, privileged axx

  
refactor

   
smell

Code smell

  
support

transparency and help with exception states

  
tooling

   
ux
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Activity
Doing
Activity
Hold
Activity
Proposal
Activity
QA
Activity
Validate
Runner
AT
Runner
CLI
Runner
HTTP
Runner
SSH
cleanup
devops
documentation
easypeasy
exchange
i18n
legacy
meta
migration
optimization
privilege
refactor
smell
support
tooling
ux
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
carlos
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: urdt/ussd#144
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?