Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@chinmaygarde
Copy link
Member

No change in functionality. I've just renamed the TU's to replace display_list_ to dl_. I am sure there are chances to make the naming better. For instance, the op receiver still being named a dispatcher.

@chinmaygarde chinmaygarde requested a review from flar April 13, 2023 23:24
Copy link
Contributor

@flar flar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My comments are "food for thought" at this point.

namespace impeller {

class DisplayListDispatcher final : public flutter::DlOpReceiver {
class DLDispatcher final : public flutter::DlOpReceiver {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DisplayList uses Dl as a prefix with a lower case L.

Also, perhaps DlImpellerDispatcher to match DlSkCanvasDispatcher?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another thought is that these naming changes seem to be creating consistency with code that is in the DL module. Should they have their own naming convention as they are the Impeller implementations of some of the DL interfaces rather than actual APIs/classes provided by DL?

@chinmaygarde
Copy link
Member Author

DisplayList uses Dl as a prefix with a lower case L.

Whoops. Fixed and made it consistent.

Should they have their own naming convention as they are the Impeller implementations of some of the DL interfaces rather than actual APIs/classes provided by DL?

I think being consistent with DL is fine as thats the interface this module is trying to adhere to.

@chinmaygarde
Copy link
Member Author

@flar PTAL?

Copy link
Contributor

@flar flar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@chinmaygarde chinmaygarde self-assigned this Apr 17, 2023
@chinmaygarde chinmaygarde added e: impeller autosubmit Merge PR when tree becomes green via auto submit App labels Apr 17, 2023
@auto-submit
Copy link
Contributor

auto-submit bot commented Apr 17, 2023

auto label is removed for flutter/engine, pr: 41174, due to - The status or check suite Windows Android AOT Engine has failed. Please fix the issues identified (or deflake) before re-applying this label.

@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Apr 17, 2023
@chinmaygarde chinmaygarde added the autosubmit Merge PR when tree becomes green via auto submit App label Apr 17, 2023
@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Apr 17, 2023
@auto-submit
Copy link
Contributor

auto-submit bot commented Apr 17, 2023

auto label is removed for flutter/engine, pr: 41174, due to - The status or check suite Mac Host clang-tidy has failed. Please fix the issues identified (or deflake) before re-applying this label.

No change in functionality. I've just renamed the TU's to replace
`display_list_` to `dl_`. I am sure there are chances to make the naming
better. For instance, the op receiver still being named a dispatcher.
@chinmaygarde chinmaygarde added the autosubmit Merge PR when tree becomes green via auto submit App label Apr 19, 2023
@auto-submit auto-submit bot merged commit 0a53cf6 into flutter:main Apr 19, 2023
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Apr 19, 2023
@chinmaygarde chinmaygarde deleted the mvdl branch August 22, 2024 19:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

autosubmit Merge PR when tree becomes green via auto submit App e: impeller

Projects

No open projects
Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants