Ticket #46266

A function for arbitrary vector requirement s evaluation

오픈 날짜: 2022-12-13 05:13 마지막 업데이트: 2022-12-17 12:10

Reporter:
소유자:
Type:
Status:
Closed
Component:
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
2

Details

A split from #46046

cazfi

"This patch includes a generic mechanism for arbitrary requirement vector evaluation (i.e., substituting is_req_active() with a custom callback)." Could you split that to a separate patch? So that unrelated functionalities would not be tied to acceptance (schedule) of this patch. I didn't look it closely, but noticed that you have parameters with _sz -suffix in their name, but which are not of type size_t. Should they?

Ticket History (3/13 Histories)

2022-12-13 05:13 Updated by: ihnatus
  • New Ticket "A function for arbitrary vector requirement s evaluation" created
2022-12-13 06:26 Updated by: ihnatus
댓글 올리기

Patch for master. Didn't test it for 3.1.

2022-12-14 05:49 Updated by: ihnatus
  • File 3.1-tri_reqs_cb_active.patch (File ID: 11090) is attached
2022-12-14 05:50 Updated by: ihnatus
댓글 올리기
(This comment has been deleted)
2022-12-14 05:53 Updated by: ihnatus
  • File 3.1-tri_reqs_cb_active.patch (File ID: 11090) is deleted
2022-12-14 06:02 Updated by: ihnatus
  • File 3.1-improve-ai-danger.patch (File ID: 11092) is attached
2022-12-14 06:02 Updated by: ihnatus
댓글 올리기

A patch working with 3.1 is added.

2022-12-14 06:03 Updated by: ihnatus
  • File 3.1-improve-ai-danger.patch (File ID: 11092) is deleted
2022-12-14 09:52 Updated by: cazfi
댓글 올리기

Reply To ihnatus

A patch working with 3.1 is added.

I think that requires backporting #45020 first.

2022-12-14 14:33 Updated by: cazfi
  • 소유자 Update from ihnatus to cazfi
  • Resolution Update from None to Accepted
2022-12-17 12:10 Updated by: cazfi
  • Status Update from Open to Closed
  • Resolution Update from Accepted to Fixed

Edit

Please login to add comment to this ticket » Login