Ticket #569 (closed roadmap: invalid)

Opened 5 years ago

Last modified 3 years ago

vtable swap (e.g. bignum)

Reported by: coke Owned by: chromatic
Priority: normal Milestone: 2.6
Component: core Version:
Severity: medium Keywords:
Cc: cotto Language:
Patch status: Platform:

Change History

follow-up: ↓ 8   Changed 5 years ago by whiteknight

Can we get some information here about what this task requires, who is working on it, and what effort is needed to get it complete?

  Changed 5 years ago by allison

  • owner set to chromatic
  • milestone changed from 1.2 to 1.3

  Changed 5 years ago by allison

  • milestone changed from 1.3 to 1.5

  Changed 5 years ago by jkeenan

  • component changed from none to core

  Changed 5 years ago by allison

  • milestone changed from 1.5 to 1.7

  Changed 5 years ago by chromatic

Refactoring the Key PMCs has lessened the need for this; I recommend unscheduling from the 2.0 series.

  Changed 5 years ago by allison

  • milestone changed from 1.7 to 2.6

in reply to: ↑ 1   Changed 3 years ago by jkeenan

  • cc cotto added

Replying to whiteknight:

Can we get some information here about what this task requires, who is working on it, and what effort is needed to get it complete?

Same question applies 22 months later? Can we get an update?

Thank you very much.

kid51

  Changed 3 years ago by cotto

  • status changed from new to closed
  • resolution set to invalid

I'm rejecting this, mostly because the need and plan for implementing vtable swapping are stuck in chromatic's head. As it stands now, it's not possible to evaluate whether this is something worth pursing. I'm not opposed to the idea, but there needs to at least be a description to work from.

Note: See TracTickets for help on using tickets.